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/perf)<a href="https://agentmods.dev/commands/smrafiz/claude-supercharger/perf"><img src="https://agentmods.dev/badge/commands/smrafiz/claude-supercharger/perf.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.00382 |
| Opus 5 | $0.00000 | $0.00191 |
| Sonnet 5 | $0.00000 | $0.00076 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
perf 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 8d 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 performance timing report. Options: $ARGUMENTS (e.g. --slow, --days 7)
Run the hook performance profiler and display results.
Step 1 — Run the report
bash ${CLAUDE_PLUGIN_ROOT}/tools/hook-perf.sh $ARGUMENTS
If the command exits with "No hook timing data found", explain:
- On bash 5+ (zero-fork
EPOCHREALTIMEclock), hooks slower than ~40ms are recorded automatically — no setup; just use Claude and re-run/perf. Tune withSUPERCHARGER_PERF_THRESHOLD_MS. - On bash 3.2 (macOS default — no cheap ms clock) auto-timing is off to avoid
a per-hook python fork. Check
bash --version; if 3.2, enable full profiling. - Full profiling (every hook fire, any bash):
touch ${CLAUDE_PLUGIN_DATA}/scope/.profiling, use Claude for a session, re-run/perf, thenrm ${CLAUDE_PLUGIN_DATA}/scope/.profiling.
Step 2 — Interpret results
Present the table as-is. Then add a one-line summary:
- Highlight the slowest hook (highest avg_ms)
- Note if any hook averages >200ms (flag as candidate for SUPERCHARGER_PROFILE=minimal)
- Note total overhead per Claude invocation
Step 3 — Suggest action (only if data warrants it)
If total overhead >500ms/call or any hook >200ms avg:
- Suggest
{"profile": "minimal"}in.supercharger.jsonif the slow hooks are in the minimal skip list - Otherwise name the specific hook and suggest
disableHooksif it's safe to skip
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.
- 8d ago First seen · 32 lines · 0 tokens per session scan A d5c520f8ff4f
perf 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 382 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.