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.
npx agentmods add commands/smrafiz/claude-supercharger/scopegit 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/scope)<a href="https://agentmods.dev/commands/smrafiz/claude-supercharger/scope"><img src="https://agentmods.dev/badge/commands/smrafiz/claude-supercharger/scope.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.00282 |
| Opus 5 | $0.00000 | $0.00141 |
| Sonnet 5 | $0.00000 | $0.00056 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
scope 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 6d 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
Pre-flight scope check before starting: $ARGUMENTS
Do NOT start implementation. This is a planning gate.
Step 1 — Parse the task What exactly is being asked? Restate in one sentence, no ambiguity.
Step 2 — File inventory List every file that will be created, modified, or deleted. For each:
- Path
- What changes (1 sentence)
- Risk level (low/medium/high)
Step 3 — Boundaries What files/dirs are explicitly OUT of scope? Name them.
Step 4 — Risks What could go wrong? List 2-3 specific risks (not generic).
Step 5 — Estimate Rough turn count: how many tool calls will this take?
Step 6 — Approval gate Present the scope and wait for user approval before proceeding.
Output format:
TASK: [one sentence]
FILES TO TOUCH:
Create: [path] — [what]
Modify: [path] — [what] — [risk]
Delete: [path] — [why]
OUT OF SCOPE:
- [file/dir]: [why not touching]
RISKS:
1. [risk]: [mitigation]
2. [risk]: [mitigation]
ESTIMATE: ~[N] turns
Proceed? (waiting for approval)
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.
- 6d ago First seen · 46 lines · 0 tokens per session scan A 96dfd959d7ec
scope is a command published in the GitHub repository smrafiz/claude-supercharger (11 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 282 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.