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/estimate)<a href="https://agentmods.dev/commands/smrafiz/claude-supercharger/estimate"><img src="https://agentmods.dev/badge/commands/smrafiz/claude-supercharger/estimate/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/estimate"><img src="https://agentmods.dev/badge/commands/smrafiz/claude-supercharger/estimate.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.00411 |
| Opus 5 | $0.00000 | $0.00205 |
| Sonnet 5 | $0.00000 | $0.00082 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
estimate 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
Scoped time + complexity estimate for: $ARGUMENTS
Do NOT write code. Do NOT start work. This is a report-only analysis.
Step 1 — Decompose the task List concrete subtasks (5-10 max). Each must be a discrete unit of work.
Step 2 — Estimate per subtask For each subtask, estimate:
- Files touched (count + list)
- Lines changed (rough — under 50 / 50-200 / over 200)
- Tool calls (rough — under 10 / 10-30 / over 30)
- Wall-clock time (under 15 min / 15-60 min / over 1 hour)
- Risk (low/med/high) with one-line reason
Step 3 — Identify dependencies Which subtasks block others? Critical path?
Step 4 — Surface unknowns List explicit "I don't know yet" items that would change the estimate. These need user clarification or investigation BEFORE work starts.
Step 5 — Bottom line Total estimated turns and wall-clock. Confidence level (low/med/high).
Output format:
TASK: [one sentence]
DECOMPOSITION:
1. [subtask] — [files/lines/turns/time/risk]
2. [subtask] — [files/lines/turns/time/risk]
...
CRITICAL PATH: [N] → [N] → [N] (subtasks that block downstream work)
UNKNOWNS:
- [unknown 1]: would change estimate by [+X turns / +X min]
- [unknown 2]: ...
TOTAL: ~[N] turns, ~[T] wall-clock
CONFIDENCE: [low/med/high] — [reason]
Proceed? (Estimate only — wait for user approval before any code.)
End after the report. Do not start work even if asked in the same prompt — require explicit confirmation in a separate prompt.
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 · 48 lines · 0 tokens per session scan A f484cba57f5c
estimate 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 411 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
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.