Check for leaked secrets and risky code
Scans the repo and its recent history for committed secrets and common risky patterns, and tells you what to rotate or fix first.
- Kind
- Recipe
- By
- Plexiform (@CallumJB125) self-declared
- License
- CC0-1.0
- Added
- 2026-10-10
- Updated
- 2026-10-10
- Stacks
- any
- Tools
- claude
- Tags
- security, review
- sha256
20c19ad64e52360e6729024978661c7001d01e961f47020ed65408a563f63cdd
Scans the repo and its recent history for committed secrets and common risky patterns, and tells you what to rotate or fix first.
Read-only: it plans and reports, and never changes files. Cost: Medium: reads recent history as well as the current code.
The prompt
Check this repository for leaked secrets and risky code. 1. Search tracked files for anything that looks like a leaked credential, such as API keys, tokens, private keys, passwords in config and committed .env files. 2. Search the last 200 commits too (`git log -p -200`), because a deleted secret is still in history. 3. Look for common risky patterns: string-built SQL, shell commands built from input, disabled TLS checks, eval of untrusted data, overly broad file permissions. 4. Report each finding with file, line or commit, how serious it is, and what to do (rotate the key, move it to a secret store, fix the code). Never print a full credential. Show only its first four characters. Do not change any files.
To add it: in Plexiform, open Discover in the sidebar, then Add. You see everything it contains before anything is saved.