secrets

Detect exposed secrets, credentials, API keys, and tokens in codebases and Git history.

Updated Aug 23, 2026

Search Tags:#remediation #git-history #secrets-management #secrets-detection #code-security #credential-leaks

Ready to run

npx skills add https://github.com/onesmartguy/raptor-claude-plugins --skill secrets-onesmartguy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: secrets
Source: https://github.com/onesmartguy/raptor-claude-plugins/tree/main/plugins/security/skills/secrets
Command: npx skills add https://github.com/onesmartguy/raptor-claude-plugins --skill secrets-onesmartguy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Detects exposed secrets, credentials, API keys, and tokens in code and Git history, and provides remediation guidance and prevention strategies.

Core Features & Use Cases

Secret detection in code and history
Guided remediation and best practices
Reference materials for secure coding standards and remediation playbooks

Quick Start

Scan your repository for exposed secrets and surface actionable remediation steps.

Frequently Asked Questions about secrets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I detect exposed secrets and API keys in my Git history?▼

Detect exposed secrets by scanning code repositories and Git history to identify credentials, API keys, and tokens. This process surfaces current and historical credential leaks, categorizing findings by severity to prevent unauthorized codebase access.

What is the best way to scan a code repository for credential leaks?▼

Scanning a code repository for credential leaks involves applying pattern-based detection and tool-assisted scanning with TruffleHog or Gitleaks when available. This approach identifies exposed secrets across code and Git history, delivering structured findings for remediation.

Can I use this to find secrets in CI pipelines as well as source code?▼

Yes, you can apply secret detection across code repositories, CI pipelines, and Git histories. This identifies exposed credentials, API keys, and tokens in both current source code and historical commits to prevent leaks.

How do I remediate exposed credentials found during a code security scan?▼

Remediate exposed credentials by following the actionable remediation steps surfaced during the scan. Findings are categorized by severity and include guided remediation strategies, best practices, and reference materials for secure coding standards.

Do I need TruffleHog or Gitleaks installed to perform secrets detection?▼

You do not need TruffleHog or Gitleaks installed, as the skill supports pattern-based detection independently. However, it utilizes tool-assisted scanning with TruffleHog or Gitleaks when available to enhance secret detection across codebases and Git history.