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/cleanup)<a href="https://agentmods.dev/commands/smrafiz/claude-supercharger/cleanup"><img src="https://agentmods.dev/badge/commands/smrafiz/claude-supercharger/cleanup/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/cleanup"><img src="https://agentmods.dev/badge/commands/smrafiz/claude-supercharger/cleanup.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.00544 |
| Opus 5 | $0.00000 | $0.00272 |
| Sonnet 5 | $0.00000 | $0.00109 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
cleanup 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dead code and unused-import removal for: $ARGUMENTS
Two-tier safety model. Auto-fix anything in Tier 1. Require explicit approval for Tier 2.
Tier 1 — auto-fix (safe)
Apply these directly without asking:
- Unused imports (no references in file scope)
- Unused local variables (declared, never read)
- Commented-out code blocks > 3 lines old (>30 days in git blame)
- Unreachable code (after
return,throw,process.exit,panic,os.Exit) - Empty functions/methods that are never called and have no
@override/ interface obligation - Duplicate consecutive imports
Tier 2 — require approval (risky)
Surface as a list. Do not delete without user approval:
- Functions/classes/types with zero callers in this codebase but exported (could be public API)
- Symbols referenced only in tests (could be intentional test-only utilities)
- Files that appear orphaned but match conventional plugin/loader patterns (e.g.,
routes/*.ts,migrations/*,*.module.ts) - Symbols referenced via dynamic dispatch (
getattr,require()with template, reflection)
Process
- Scan the target ($ARGUMENTS — file, directory, or whole project)
- Apply Tier 1 fixes; report what was removed (file:line for each)
- Compile Tier 2 findings into a numbered list with evidence per item:
- Symbol name
- Where defined
- Why flagged (zero callers / test-only / dynamic-dispatch suspect)
- Confidence (low/med/high)
- Run available type checks / tests after Tier 1 changes — if anything fails, halt and report
- Wait for user approval on Tier 2 items individually (not bulk)
Output format
=== Tier 1: Applied ===
- [file:line] removed unused import: [name]
- [file:line] removed unreachable code (after [return|throw])
- ...
Tests passing: [yes/no]
=== Tier 2: Awaiting approval ===
1. [symbol] @ [file:line]
- Definition: [signature]
- Why flagged: [reason]
- Confidence: [low/med/high]
- Risk if removed: [public API break / test removal / hidden dynamic call]
2. ...
Reply with the numbers you want removed (e.g., "1, 3") or "skip all".
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 · 58 lines · 0 tokens per session scan A 2d5e8ae5a014
cleanup 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 544 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.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
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.