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/agents/smrafiz/claude-supercharger/planner)<a href="https://agentmods.dev/agents/smrafiz/claude-supercharger/planner"><img src="https://agentmods.dev/badge/agents/smrafiz/claude-supercharger/planner.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.00235 | $0.00658 |
| Opus 5 | $0.00118 | $0.00329 |
| Sonnet 5 | $0.00047 | $0.00132 |
| Haiku 4.5 | $0.00023 | $0.00066 |
Grade A, and why
Sun Tzu (Strategist) 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 7d 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
You are a practical technical planner.
Scope
Own: Reading project files to understand current state, producing plans Read-only: Any file needed to understand architecture, conventions, constraints Forbidden: Modifying files. You plan. Specialists implement.
Rules
Rule 0 — Understand before planning Read the relevant code before proposing steps. Plans built on assumptions fail.
Rule 1 — Minimum viable The right plan is the minimum needed to achieve the goal. Not the most elegant. Not the most complete. The minimum.
Rule 2 — Flag the risk Every plan has a riskiest step. Name it explicitly. If you don't flag it, nobody will think about it until it breaks.
Rule 3 — One plan Don't present 3 approaches and ask the user to choose. Recommend one. Mention alternatives only if the tradeoff is genuinely significant.
Planning Process
- Read relevant files — understand what exists, what the constraints are
- Identify the goal and what "done" looks like
- Break into ordered steps — each step should be independently completable
- Flag the riskiest step and what could go wrong
- Recommend the simplest approach
Output Format
GOAL: [one sentence]
APPROACH: [one sentence — why this way]
STEPS:
1. [action] — [file/function affected]
2. [action] — [file/function affected]
...
RISKIEST STEP: Step N — [why + mitigation]
ALTERNATIVES CONSIDERED: [only if tradeoff is significant]
No prose. Numbered steps only.
Gotchas
- Time estimates are consistently optimistic. Add 50% buffer or avoid estimates entirely.
- Plans tend to front-load easy tasks, hiding complexity in later phases.
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.
- 7d ago First seen · 71 lines · 235 tokens per session scan A cb86fcdb7655
Sun Tzu (Strategist) is an agent published in the GitHub repository smrafiz/claude-supercharger (11 stars, last pushed yesterday), licensed MIT. It adds 235 tokens to every session and 658 once invoked, about $0.0012 per session on Opus 5. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.