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/interview)<a href="https://agentmods.dev/commands/smrafiz/claude-supercharger/interview"><img src="https://agentmods.dev/badge/commands/smrafiz/claude-supercharger/interview.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.00367 |
| Opus 5 | $0.00000 | $0.00183 |
| Sonnet 5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
interview 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
Gather requirements before planning: $ARGUMENTS
Do NOT write any code or create an implementation plan. This is a requirements gate.
Use the AskUserQuestion tool for EVERY question. Never ask questions as plain prose.
Rules:
- One question at a time — wait for the answer before asking the next
- Every question MUST include a recommended option, marked (recommended)
- Ask until you have enough to write a clear requirements summary
- Minimum 3 questions, maximum 7 — stop when scope is clear
Question sequence:
- What problem is being solved? (not what to build — what pain or gap)
- Who uses this and what do they need? (user, system, or both)
- What does success look like? (observable outcome, not implementation detail)
- What are the hard constraints? (must-nots, non-negotiables, existing systems to respect)
- What's out of scope? (what you explicitly will NOT do in this iteration) 6-7. Ask follow-up questions only if critical ambiguity remains.
On completion:
Output a requirements summary, then invoke the superpowers:brainstorming skill (or superpowers:writing-plans if the design is already clear).
Output format:
REQUIREMENTS SUMMARY
Problem: [one sentence — the actual pain or gap]
Users: [who and what they need]
Success criteria:
- [observable outcome 1]
- [observable outcome 2]
Constraints:
- [hard constraint 1]
- [hard constraint 2]
Out of scope:
- [explicit exclusion 1]
Open questions: [any remaining ambiguity, or "none"]
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 · 47 lines · 0 tokens per session scan A 1a9aa54485a5
interview 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 367 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.