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 skills add sramji/awesome-superpowers --skill awesome-writing-plansgit clone --depth 1 https://github.com/sramji/awesome-superpowersWrote 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/skills/sramji/awesome-superpowers/awesome-writing-plans)<a href="https://agentmods.dev/skills/sramji/awesome-superpowers/awesome-writing-plans"><img src="https://agentmods.dev/badge/skills/sramji/awesome-superpowers/awesome-writing-plans/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/skills/sramji/awesome-superpowers/awesome-writing-plans"><img src="https://agentmods.dev/badge/skills/sramji/awesome-superpowers/awesome-writing-plans.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.00089 | $0.02023 |
| Opus 5.5 | $0.00036 | $0.00809 |
| Sonnet 5.5 | $0.00018 | $0.00405 |
| Haiku 4.5 | $0.00009 | $0.00202 |
Grade A, and why
awesome-writing-plans 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Awesome Writing Plans
Overview
Project-level wrapper for superpowers:writing-plans that adds a fresh-subagent rigor review loop after the plan is written and before handoff to executing-plans. Each round asks "what realistic failure mode would survive these tests?" and the main agent either extends the plan with a closing test or marks the gap out-of-scope with a written rationale. Loop runs up to 3 rounds; terminates on 0 critical gaps or escalates to the user with a summary.
Announce at start: "I'm using the awesome-writing-plans skill — write the plan with a ≤3-round test-rigor pass before handoff."
Core principle: Run upstream writing-plans → Pass B rigor loop → extend or defer each critical gap → handoff to executing-plans.
The Process
digraph awesome_writing_plans {
rankdir=TB;
upstream [label="Step 1: Run\nsuperpowers:writing-plans" shape=box];
written [label="Plan written" shape=box];
self_review [label="Upstream Self-Review\n(inline checklist)" shape=box];
round [label="Step 2: Pass B Round N\nDispatch subagent" shape=box];
gaps [label="Critical gaps\nreturned?" shape=diamond];
address [label="Extend plan OR\nadd to Deferred Risks" shape=box];
cap [label="Round count\n≥ 3?" shape=diamond];
escalate [label="Escalate to user\nwith summary" shape=box];
handoff [label="Step 3: Handoff to\nexecuting-plans" shape=doublecircle];
upstream -> written;
written -> self_review;
self_review -> round;
round -> gaps;
gaps -> address [label="yes"];
gaps -> handoff [label="no"];
address -> cap;
cap -> escalate [label="yes"];
cap -> round [label="no"];
escalate -> handoff;
}
Step 1: Run upstream writing-plans
Invoke superpowers:writing-plans.
Run it to completion through its own "Self-Review" step. Do not proceed to the upstream skill's "Execution Handoff" step until Pass B runs (Step 2). The override inserts between self-review and execution-handoff.
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.
- 2mo ago First seen · 189 lines · 89 tokens per session scan A d653f6f3b6fe
awesome-writing-plans is a skill published in the GitHub repository sramji/awesome-superpowers (3 stars, last pushed 3mo ago), licensed MIT. It adds 89 tokens to every session and 2,023 once invoked, about $0.0004 per session on Opus 5.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 skills, from other repositories
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
health
Audits agent config, instruction drift, hooks or MCP, and AI maintainability. Use when Claude, Codex, or Pi setup looks wrong. Not for application bugs or PR review.
hunt
Finds root cause before any fix. Use when something errors, crashes, regresses, or used to work. Not for code review or new features.
tdd
You MUST use this when implementing testable behavior changes - new features, bug fixes, or refactors with observable contracts. Covers writing meaningful failing tests before implementation and verifying behavior through the red-green-refactor cycle. Not for purely mechanical edits without behavior changes.
vitest
You MUST use this when configuring, writing, debugging, running, migrating, or auditing Vitest tests in JavaScript/TypeScript projects - Vite, Vue, Nuxt, React, Next.js, Node libraries, workspaces, coverage, mocks, snapshots, flaky tests, CI parity, or Jest migration.
web-debug
You MUST use this when interacting with or testing local web applications with Playwright - verifying frontend functionality, debugging UI behavior, capturing browser screenshots, or viewing browser console logs.