Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add smrafiz/claude-supercharger/plugin install 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-clear)<a href="https://agentmods.dev/commands/smrafiz/claude-supercharger/cache-clear"><img src="https://agentmods.dev/badge/commands/smrafiz/claude-supercharger/cache-clear/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/cache-clear"><img src="https://agentmods.dev/badge/commands/smrafiz/claude-supercharger/cache-clear.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.00011 | $0.00232 |
| Opus 5.5 | $0.00004 | $0.00093 |
| Sonnet 5.5 | $0.00002 | $0.00046 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade A, and why
cache-clear 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 15d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- sc-cache-clear — 91% identical, 4 lines differ
What it actually says
Clear typecheck and quality-gate hash caches. Arguments: $ARGUMENTS
Runs tools/cache-clear.sh to remove all cached hash files so hooks re-check all files on next run.
if [ -f "${CLAUDE_PLUGIN_ROOT}/tools/cache-clear.sh" ]; then
bash "${CLAUDE_PLUGIN_ROOT}/tools/cache-clear.sh" $ARGUMENTS
else
echo "cache-clear.sh not found. Re-run install.sh to restore tools."
fi
Options:
- No args — clears all cache files immediately
--dry-run— shows what would be removed without deleting
When to use:
- After moving or renaming files (stale keys from old paths won't prune themselves until next write)
- After a hook misconfiguration produced incorrect cache entries
- When forcing a full re-check for a security audit
After running, the next hook execution will re-hash all files from scratch.
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.
- 15d ago Changed · -5 tokens per session 00cda69e7f88
- 17d ago Changed · +3 lines · +16 tokens per session 64eea8c0b540
- 1mo ago First seen · 25 lines · 0 tokens per session scan A 9321ff55b40f
cache-clear is a command published in the GitHub repository smrafiz/claude-supercharger (15 stars, last pushed 2d ago), licensed MIT. It adds 11 tokens to every session and 232 once invoked, about $0.0000 per session on Opus 5.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-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.