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/system-audit)<a href="https://agentmods.dev/commands/fatihkan/badi/system-audit"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/system-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.1 | $0.00000 | $0.01010 |
| Opus 5 | $0.00000 | $0.00505 |
| Sonnet 5 | $0.00000 | $0.00202 |
| Haiku 4.5 | $0.00000 | $0.00101 |
Grade A, and why
system-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 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.
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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep infrastructure audit command. Comprehensively audits all Badi components across 9 checkpoints.
Required Tools
- Read (all config files) -- Grep (reference/pattern scan) -- Glob (file existence) -- Bash (permissions, JSON validation, file info) -- Write (report)
Procedure (9 Checks)
Check 1: Agent Health
- List the
.claude/agents/files - Each agent: YAML frontmatter format -- required fields (name, description, tools) -- are referenced tools valid -- unresolved
{{...}}-- instruction consistency - Agent count and status summary
Check 2: Command Health
- List the
.claude/commands/files - Each command: description line -- tool requirements -- procedure steps -- output format -- valid markdown
command-index.mdcross-reference: in the index but no file -- file exists but not in the index -- description mismatch
Check 3: Hook Health
- Validate
settings.jsonJSON - Each hook: does the file exist -- executable permission -- dry run (syntax) -- correct trigger
- Run order/priority -- colliding/conflicting hooks
Check 4: Memory Layer
memory.md: size (500-line limit) -- freshness (last update) -- internal consistency (contradicting info) -- source attributionknowledge-base.md: size (1000-line limit) -- categorization -- unverified information -- citation/reference
Check 5: Log Health
- Directories:
daily-notes/,handoffs/size/count -- audit trail files (audit-trail.md, incident-log.md, failure-log.md) - Each log: size limit -- format consistency -- date accuracy
- JSONL (verdicts.jsonl): each line valid JSON -- schema consistency
Check 6: Permissions/Configuration
- Hook file permissions -- do references inside settings.json exist -- environment variable dependencies (used but undefined) -- directory structure -- sensitive-file check against
.gitignore
Check 7: Cross-Consistency
- If A references B, does B exist -- circular dependencies -- orphan references (unlinked files) -- CLAUDE.md ↔ command/agent behavior alignment -- naming conventions
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 · 90 lines · 0 tokens per session scan A 0547f87bc532
system-audit 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,010 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.
Other commands, from other repositories
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524) — sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
investigate
Systematic root-cause debugging — find the cause before writing any fix.
optimize
Analyze and suggest performance improvements for code, queries, or systems.
diagnose
Interactive troubleshooting assistant for Claude Code issues.
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.