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/smrafiz/claude-superchargerWrote 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/smrafiz/claude-supercharger/audit)<a href="https://agentmods.dev/commands/smrafiz/claude-supercharger/audit"><img src="https://agentmods.dev/badge/commands/smrafiz/claude-supercharger/audit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/smrafiz/claude-supercharger/audit"><img src="https://agentmods.dev/badge/commands/smrafiz/claude-supercharger/audit.svg" alt="Reviewed on agentmods" width="80" 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.00295 |
| Opus 5 | $0.00000 | $0.00148 |
| Sonnet 5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00030 |
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 9d 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.
What it actually says
Sweep $ARGUMENTS for inconsistencies. Read the relevant files first, then check each dimension.
Dimensions:
-
Naming — Are conventions applied consistently? Check: camelCase vs snake_case, plural vs singular, verb-noun patterns, abbreviations. Flag when the same concept is named differently in different places.
-
Patterns — Is the same problem solved different ways in different places? Check: error handling style, async patterns, state management, data fetching, logging.
-
Documentation — Do comments, README, and inline docs match what the code actually does? Flag outdated docs, missing docs for public interfaces, and misleading comments.
-
Interfaces — Are API contracts, function signatures, or types inconsistent with their actual usage? Flag mismatches between what a function promises and what callers expect.
-
Structure — Do similar modules follow the same layout? Check: file organization, export patterns, test file placement.
Output format:
## INCONSISTENCIES FOUND
[dimension]
- [file:line] vs [file:line] — [what conflicts] — established pattern: [which is correct based on majority usage]
## PATTERN RECOMMENDATIONS
- [what the consistent pattern should be, with example]
## CLEAN — no issues found in:
- [dimension]: consistent throughout
Read-only. Flag only — do not fix. Skip dimensions with no findings.
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.
- 9d ago First seen · 30 lines · 0 tokens per session scan A 86c15775287c
audit is a command published in the GitHub repository smrafiz/claude-supercharger (11 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 295 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-30.
Other commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.
security-review
AI-powered security review of the current git diff (or specified paths). Dispatches the security-reviewer agent and prints findings grouped by severity.