A project-wide scan for exposed passwords, API keys, tokens, database connection strings, and private keys. It can check current files and, optionally, Git history.

Use it before commits or in continuous integration (automated checks run during code changes) to scan files or history and return findings in text or JSON.

It helps find credentials that may have been committed to a codebase, where others could misuse them.

secret-scan — Command for Claude Code by fatihkan

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/fatihkan/badi

Made for: Claude Code.

Or install badi, the plugin that ships this one along with the rest of its 81 skills, 86 commands, 30 agents, 7 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/fatihkan/badi/secret-scan.svg)](https://agentmods.dev/commands/fatihkan/badi/secret-scan)

Your own site

<a href="https://agentmods.dev/commands/fatihkan/badi/secret-scan"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/secret-scan.svg" alt="Measured on agentmods" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 637 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00637
Opus 5	$0.00000	$0.00318
Sonnet 5	$0.00000	$0.00127
Haiku 4.5	$0.00000	$0.00064

Measured yesterday against content hash 6fa9522447bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

secret-scan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/secret-scan.md · 64 lines

How it starts

The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Project-wide secret/credential scan command. AWS/GCP/GitHub/npm/Stripe/OpenAI/Anthropic keys, JWTs, database URIs, private keys.

For wider coverage: badi security baseline (secret-scan + npm audit), /security-review (Anthropic native AI semantic — Claude Code 2.1.140+).

Required Tools

Bash (badi secret-scan command invocation)

Procedure

Step 1: Define the Scope

Ask the user:

Working tree only? (fast)
Include git history? (default 100 commits; raise with --max-commits)
For CI/pipelines? (--exit-code strict + --format json)

Step 2: Run the Scan

badi secret-scan                                       # Working tree
badi secret-scan --git                                 # + git history
badi secret-scan --format json                         # JSON output
badi secret-scan --exit-code strict                    # exit 1 on any finding
badi secret-scan --max-commits 500 --git               # deeper history
badi secret-scan --ignore jwt,github-pat-fine          # ignore specific patterns
badi secret-scan --ignore-file .secretignore           # read from a file
badi secret-scan --patterns custom-org-patterns.json   # load extra patterns

CI exit codes:

0 No findings (or --exit-code never; or only MEDIUM/LOW by default)
1 CRITICAL or HIGH finding

Out of scope: symlinks are skipped; git stash/reflog/packed-refs are not scanned.

Step 3: Interpret the Results

By severity:

CRITICAL: AWS Access/Secret, GCP, GitHub PAT (classic + fine-grained), Slack, Stripe, OpenAI, Anthropic, RSA/EC private keys
HIGH: npm token, SendGrid, Twilio, MongoDB/Postgres URIs
MEDIUM: JWT tokens
LOW: Generic secret variables (high false-positive risk — --ignore generic-secret helps)

Step 4: Action Plan

For every finding:

Rotate — Invalidate the secret immediately (it may live in git log)
Gitignore — Add the .env or secret file to .gitignore
Environment variables — Use process.env.X instead of hardcoded values
Git history cleanup — Use git filter-repo or BFG

Read the full file on GitHub · 64 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 64 lines · 0 tokens per session scan A 6fa9522447bc

Subscribe to this mod's changes

secret-scan is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 637 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-06.

Security agents ai-workflow cli developer-tools hooks

secret-scan

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Required Tools

Procedure

Step 1: Define the Scope

Step 2: Run the Scan

Step 3: Interpret the Results

Step 4: Action Plan

What this file has done since we first saw it

Other commands, from other repositories

audit-agents-skills

check-cache-bugs

land-and-deploy

qa

review-pr

security-audit