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/random6913/claude-code-superkit/auditgit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWrote 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/random6913/claude-code-superkit/audit)<a href="https://agentmods.dev/commands/random6913/claude-code-superkit/audit"><img src="https://agentmods.dev/badge/commands/random6913/claude-code-superkit/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.00020 | $0.01995 |
| Opus 5 | $0.00010 | $0.00997 |
| Sonnet 5 | $0.00004 | $0.00399 |
| Haiku 4.5 | $0.00002 | $0.00199 |
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 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Orchestrator
Dispatch specialized audit agents in parallel and merge their reports into one unified audit report with a Grand Summary.
Hard Rules
- Dispatch all selected agents in parallel — a single message with multiple Agent tool calls.
- Only dispatch agents that exist in the project's
.claude/agents/directory. Skip unavailable agents with a note — never invent results for an agent that did not run. - Quote each agent's verdicts verbatim: audit-frontend / audit-backend / audit-infra each return exactly 12 checks with per-check
PASS/WARN/FAILplus notes; security-scanner returns findings withCRITICAL/WARNING/SUGGESTION. Never relabel one enum as the other — the only cross-mapping allowed is the Section Verdict table in Step 6. - Emit the Grand Summary ONLY after every dispatched agent has returned or its section is explicitly marked SKIPPED.
- Grand Summary counts are copied from each agent's own
Summary:line — each dispatched auditor row must sum to 12; the Total row must equal the column sums. - The audit is read-only — never modify project files.
- Unrecognized scope argument → run
alland stateunrecognized scope '<arg>' — defaulted to allin the report header.
Steps
1. Parse scope and mode
Consume $ARGUMENTS:
| Arguments | Action |
|---|---|
contain --health |
Health mode → Step 2 |
frontend | backend | infra | security | all |
That scope → Step 3 |
| empty | Scope all → Step 3 |
| anything else | Scope all + header note (Hard Rule 7) → Step 3 |
Done when: exactly one scope, or health mode, is selected.
2. Health mode (only when --health)
Dispatch ONLY the health-checker agent (skip frontend/backend/infra/security audits) with:
Run all your health checks against the project codebase and emit your Project Health Dashboard.
Output health-checker's own Output Contract verbatim — the Project Health Dashboard block. The unified template below does NOT apply to health mode. If health-checker is not in .claude/agents/, report "health-checker unavailable — cannot run health mode" and stop.
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 · 167 lines · 20 tokens per session scan A c65809dabff9
audit is a command published in the GitHub repository RaNDoM6913/claude-code-superkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 1,995 once invoked, about $0.0001 per session on Opus 5. 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-03.
Other commands, from other repositories
copy-ai-context
Export converged workspace context to the clipboard for any AI chat.
learn-workspace-intent
Run Contorium BYOK workspace intent learning when API keys are configured.
setup-mcp-claude-code
Build and register the Contorium MCP server for Claude Code or Cursor Agent.
start-fresh-session
Start a fresh Contorium AI context session after a major task or workspace shift.
setup-mcp-codex
Build Contorium and install the Codex plugin with bundled MCP memory tools.
dmb-resume
Resume DMB context for this session.