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.
npx agentmods add commands/fatihkan/badi/auditgit 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/audit)<a href="https://agentmods.dev/commands/fatihkan/badi/audit"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/audit.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 | $0.00000 | $0.00844 |
| Opus 5 | $0.00000 | $0.00422 |
| Sonnet 5 | $0.00000 | $0.00169 |
| Haiku 4.5 | $0.00000 | $0.00084 |
Grade A, and why
audit 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 4d ago.
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.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality audit command. Runs a systematic audit over code, structure, or process.
Badi CLI Commands (v1.6+)
A Level T4 (Comprehensive) audit runs these CLI tools:
badi secret-scan --git— Secret scan + git historybadi lighthouse [url]— Performance + Core Web Vitalsbadi a11y [url]— Accessibility (WCAG 2.1)badi ssl/dns/whois [domain]— Domain health (if production exists)badi commit --check— Last commit conventional format
Required Tools
- Read (file reading)
- Grep (code scan)
- Glob (file discovery)
- Bash (analysis tools)
- Write (report writing)
Procedure (5 Steps)
Step 1: Define the Scope
Ask the user: "Pick the audit scope:"
- File/Directory: A specific file or folder
- Module: A whole module or feature
- Project-Wide: The entire codebase
- Process: CI/CD, test, deploy processes
Step 2: Pick the Audit Level (T1-T4)
T1 - Quick Scan (2-5 min)
- Syntax and format checks
- Obvious security issues (hardcoded secrets, SQL injection)
- Missing files or broken imports
- Lint rule violations
T2 - Standard Audit (5-15 min)
- T1 + code quality metrics
- Duplicated code (DRY violations)
- Naming consistency
- Comment and documentation gaps
- Test coverage analysis
T3 - Deep Audit (15-30 min)
- T2 + architectural fit analysis
- Dependency graph review
- Performance bottlenecks
- Error handling patterns
- Access control and authorization
T4 - Comprehensive Audit (30+ min)
- T3 + security scan (OWASP Top 10)
- Scalability assessment
- Disaster recovery readiness
- Compliance checks (licenses, GDPR/KVKK, etc.)
- Technical debt inventory
- Badi CLI Extras:
badi secret-scan --git— Secrets + git historybadi lighthouse [url]— Performance + SEO + A11y + Best Practicesbadi a11y [url]— WCAG 2.1 detailbadi ssl/dns/whois [domain]— Production domain healthbadi commit --check— Commit format compliance
Step 3: Delegate to the Audit Agent
Start the audit at the chosen level:
- Mark every check item PASS / FAIL / WARN
- Collect and classify the findings
- Attach evidence (code lines, file paths)
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.
- 4d ago First seen · 115 lines · 0 tokens per session scan A 6d7058c3596c
audit is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 844 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-08-31.
Other commands, from other repositories
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
sonarqube
Analyze SonarCloud quality issues for a specific PR.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
methodology-advisor
Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack.
scaffold
Interactive coach that asks 4-5 questions to determine whether you need an agent, command, skill, hook, or rule — then generates a ready-to-use template. Usage: /scaffold (no arguments — starts the coaching session).
investigate
Systematic root-cause debugging — find the cause before writing any fix.