secret-detection-scanner
Detect secrets, credentials, and sensitive data in code and configurations. Scan git history for secrets, detect API keys, tokens, passwords, check environment files, monitor CI/CD logs for exposure, generate remediation steps, and track secret rotation status.
npx skills add a5c-ai/babysitter --skill secret-detection-scanner --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# secret-detection-scanner You are **secret-detection-scanner** - a specialized skill for detecting secrets, credentials, and sensitive data in code, configurations, and git history. This skill provides comprehensive capabilities for preventing secret exposure and managing credential security. ## Overview This skill enables AI-powered secret detection including: - Gitleaks secret scanning in code and git history - TruffleHog deep commit scanning - detect-secrets baseline management - API key, token, and password detection - Pre-commit hook integration - CI/CD pipeline secret monitoring - Remediation guidance and rotation tracking ## Prerequisites - Git repository to scan - CLI tools: gitleaks, trufflehog, detect-secrets (as needed) - Git for history scanning - Pre-commit framework (optional) ## Capabilities ### 1. Gitleaks Secret Scanning Fast and comprehensive secret detection: ```bash # Scan current directory gitleaks detect --source . --report-format json --report-path gitleaks-report.json # Scan with verbose output gitleaks detect --source . -v --report-format json --report-path gitleaks-report.json # Scan git history gitleaks detect --source . --log-opts="--all" --report-forma
- Overview
- Prerequisites
- Capabilities
- 1. Gitleaks Secret Scanning
- 2. TruffleHog Deep Scanning
- 3. detect-secrets Baseline Management
- 4. Pre-commit Integration
- 5. CI/CD Integration
- 6. Secret Categories and Patterns
- 7. Remediation Workflow
- 8. Secret Rotation Tracking
- MCP Server Integration
- Best Practices
- Prevention
Scan current directory gitleaks detect --source . --report-format json --report-path gitleaks-report.json Scan with verbose output gitleaks detect --source . -v --report-format json --report-path gitleaks-report.json Scan git history gitleaks detect --source . --log-opts="--all" --report-format json Scan specific commits gitleaks detect --source . --log-opts="HEAD~10..HEAD" --report-format json Scan with custom config gitleaks detect --source . --config .gitleaks.toml --report-format json
What does the secret-detection-scanner skill do?
Detect secrets, credentials, and sensitive data in code and configurations. Scan git history for secrets, detect API keys, tokens, passwords, check environment files, monitor CI/CD logs for exposure, generate remediation steps, and track secret rotation status.
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill secret-detection-scanner --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.