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.
git clone --depth 1 https://github.com/fatihkan/badiWrote 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.
[](https://agentmods.dev/commands/fatihkan/badi/security-scan)<a href="https://agentmods.dev/commands/fatihkan/badi/security-scan"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/security-scan.svg" alt="Measured on agentmods" height="20"></a>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.01233 |
| Opus 5 | $0.00000 | $0.00616 |
| Sonnet 5 | $0.00000 | $0.00247 |
| Haiku 4.5 | $0.00000 | $0.00123 |
Grade A, and why
security-scan scanned grade A with 1 finding 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 today.
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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Command injection: `exec()`, `eval()`, `child_process` usage How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security scan. Searches the codebase and dependencies for vulnerabilities and produces a severity-ranked report.
Native command (v1.31.0+): With Claude Code 2.1.140+,
/security-reviewis now a native command (built-in slash). This command complements it with a deterministic baseline (badi security baseline) + post-scan triage (badi security triage).Recommended flow:
badi security baseline— secrets + dependencies (deterministic)/security-review— AI semantic vulnerability hunt (Anthropic native)badi security triage— report severity filtering- CI:
badi security init --ci— automatic review on PRs
Badi CLI Commands (v1.6+)
This command first invokes these CLI tools:
badi secret-scan— 17-pattern secret/credential scan (AWS, GCP, GitHub, OpenAI, Stripe, DB URIs, private keys)badi secret-scan --git— Also scan the last 100 commitsbadi a11y [url]— Accessibility (part of the security audit) Then it delegates to the security-scanner agent (code pattern analysis).
Required Tools
- Bash (npm audit, dependency scan)
- Read (configuration files)
- Grep (code pattern scan)
- ...
Agent Delegation
This command delegates the main scan to the security-scanner agent. If the agent is unavailable, apply the steps below directly.
Section 1: Dependency Vulnerability Scan
Step 1: Package Manager Detection and Audit
- npm: run
npm audit --json - yarn: run
yarn audit --json - pip: run
pip auditorsafety check - ...
Step 2: Vulnerability Classification
Record per finding:
- Package name and version
- CVE number (if any)
- Severity: CRITICAL / HIGH / MEDIUM / LOW
- ...
Step 3: Dependency Chain Analysis
- Determine direct vs. transitive dependency
- For transitive ones, show which parent package pulls it in
- Verify the lock file is current
Section 2: Code Pattern Analysis
Step 4: Hardcoded Secret Scan
Run badi secret-scan first — a fast scan with 17 patterns:
- AWS Access/Secret, GCP, GitHub PAT (classic + fine-grained), Slack, Stripe, OpenAI, Anthropic
- npm, SendGrid, Twilio, MongoDB/Postgres URIs
- RSA/EC private keys, JWT tokens
- Generic secrets (20-64 chars)
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.
- today First seen · 142 lines · 0 tokens per session scan A 47f4f2ae3fb5
security-scan is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,233 tokens. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-06.
Other commands, from other repositories
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524) — sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
qa
Systematic QA testing of a web application — diff-aware, tiered, with fix-and-verify loop.
review-pr
Perform a comprehensive code review of a pull request.
security-audit
Comprehensive security audit with scored posture assessment.