Secrets Scanner
$2.99OfficialScan codebases for leaked credentials, API keys, and tokens: pattern matching, entropy analysis, and safe remediation.
What you get
- ✓9-step procedure
- ✓6 pitfalls to avoid
- ✓Installs into 6 tools
- Version
- v1 →
- Last updated
- today
- Length
- 4 min read
- Requires
- Best with a strong model (Claude Sonnet 4)
Works in: Claude Code, Codex, Cline, opencode, OpenClaw, Hermes · Handles multi-file projects
Preview
When to use
Use this skill when you need to find leaked secrets in a codebase, scan a pull request before merge, triage a leak discovered post-hoc, or set up preventative secret scanning in CI. It covers both shallow pattern matching and deeper entropy/heuristic analysis, plus the safe-remediation workflow that is critical once a real secret is found. Do not use it to scan running processes or memory (runtime secret detection is a different discipline), and do not confuse it with SAST/DAST — it targets credentials, not generic code vulnerabilities.
Inputs to gather
- Repository root and scope: which directories to scan, and which to exclude (vendored code,
node_modules, generated
…
🔒 Buy once ($2.99) to unlock the full playbook, download it, and install it in every tool you use.