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/cache-stats)<a href="https://agentmods.dev/commands/smrafiz/claude-supercharger/cache-stats"><img src="https://agentmods.dev/badge/commands/smrafiz/claude-supercharger/cache-stats.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.00409 |
| Opus 5 | $0.00000 | $0.00204 |
| Sonnet 5 | $0.00000 | $0.00082 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
cache-stats 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 7d 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
Show hook cache statistics for typecheck and quality-gate. Arguments: $ARGUMENTS
Run this inline Python to report cache state:
python3 << 'EOF'
import os, json, glob, time
scope = os.path.expanduser("${CLAUDE_PLUGIN_DATA}/scope")
def report_cache(label, pattern):
files = glob.glob(os.path.join(scope, pattern))
if not files:
print(f"{label}: no cache files found")
return
total_entries = 0
stale = 0
for path in files:
try:
with open(path) as f:
d = json.load(f)
entries = len(d)
dead = sum(1 for k in d if not os.path.exists(k))
age_days = (time.time() - os.path.getmtime(path)) / 86400
print(f"{label} [{os.path.basename(path)}]: {entries} entries, {dead} stale, last written {age_days:.1f}d ago")
total_entries += entries
stale += dead
except Exception as e:
print(f"{label} [{os.path.basename(path)}]: unreadable ({e})")
print(f" Total: {total_entries} entries, {stale} stale across {len(files)} project(s)")
report_cache("typecheck ", ".typecheck-cache-*")
report_cache("quality-gate", ".quality-gate-cache-*")
EOF
After showing output, interpret it:
- stale > 0: stale entries exist but will self-prune on next cache write — no action needed
- no cache files: caches haven't been written yet (hooks haven't run a clean pass on any file)
- age > 7d: cache may be for a project no longer active — mention it but don't delete
- large entry count (>500): note it, suggest it's normal for large codebases
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.
- 7d ago First seen · 42 lines · 0 tokens per session scan A f8d18fb9f918
cache-stats is a command published in the GitHub repository smrafiz/claude-supercharger (11 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 409 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
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.