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/leodorareluctant259/superpowers-zh/write-plangit clone --depth 1 https://github.com/Leodorareluctant259/superpowers-zhWrote 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/leodorareluctant259/superpowers-zh/write-plan)<a href="https://agentmods.dev/commands/leodorareluctant259/superpowers-zh/write-plan"><img src="https://agentmods.dev/badge/commands/leodorareluctant259/superpowers-zh/write-plan.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.00015 | $0.00055 |
| Opus 5 | $0.00008 | $0.00028 |
| Sonnet 5 | $0.00003 | $0.00011 |
| Haiku 4.5 | $0.00002 | $0.00006 |
Grade A, and why
write-plan 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 5d 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
告诉你的搭档这个命令已弃用，将在下个主要版本中移除。他们应该让你使用"superpowers writing-plans"技能。
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.
- 5d ago First seen · 6 lines · 15 tokens per session scan A 09b361039c09
write-plan is a command published in the GitHub repository Leodorareluctant259/superpowers-zh (5 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 55 once invoked, about $0.0001 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-31.
Other commands, from other repositories
init
Initialize configurations for Supabase local development.
secrets
Provides tools for managing environment variables and secrets for your Supabase project.
stop
Stops the Supabase local development stack.
bump-plugin
Bump changed plugin and marketplace version.
session-stop
Stop recording and save this agent session to the project ledger.
wa-guardrails
Generate preventive Well-Architected guardrails — AWS Config rules, Service Control Policies, permission boundaries, CloudWatch alarms, and IaC policy checks (CDK Aspects, cfn-guard, OPA/Sentinel) — so a workload stays aligned with Well-Architected best practices over time instead of being assessed once.