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 dev-toolings/superpowers-symfony --skill writing-plansgit clone --depth 1 https://github.com/dev-toolings/superpowers-symfonyWrote 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/dev-toolings/superpowers-symfony/writing-plans)<a href="https://agentmods.dev/skills/dev-toolings/superpowers-symfony/writing-plans"><img src="https://agentmods.dev/badge/skills/dev-toolings/superpowers-symfony/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/dev-toolings/superpowers-symfony/writing-plans"><img src="https://agentmods.dev/badge/skills/dev-toolings/superpowers-symfony/writing-plans.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00020 | $0.00340 |
| Opus 5.5 | $0.00008 | $0.00136 |
| Sonnet 5.5 | $0.00004 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
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 20d 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
Writing Plans (Symfony)
Use when
- A feature touches several layers: entities, services, API, async work.
- The work must be reviewed, or split across sessions, before coding starts.
- Scope and risks must be known before committing to an approach.
Default workflow
- Write the overview: summary, scope in and out, dependencies.
- Design the changes: new and modified entities, services and handlers, API endpoints.
- Break the work into phases of atomic steps, each starting with its test.
- Mark the dependencies between steps and size each one (S, M, L).
- Write the acceptance criteria, and the risks with their mitigation.
Guardrails
- Every step can be completed and tested on its own.
- Name concrete files, classes and endpoints, not intentions.
- List what is out of scope instead of dropping it silently.
- Start from a template in
reference.md(CRUD, background job, integration) when one fits.
Progressive disclosure
- Use this file for execution posture and risk controls.
- Open references when deep implementation details are needed.
Output contract
- A plan with overview, design, steps, acceptance criteria and risks.
- Step dependencies and sizes.
- Open questions for the reviewer.
References
reference.md
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 20d ago Changed · +2 lines b6bff7f3ba52
- 1mo ago Changed · +2 lines · -3 tokens per session 452378b73f23
- 1mo ago First seen · 40 lines · 23 tokens per session scan A 38c4fe74ecc8
writing-plans is a skill published in the GitHub repository dev-toolings/superpowers-symfony (226 stars, last pushed 20d ago), licensed MIT. It adds 20 tokens to every session and 340 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
spine-design
Produce a system design doc — components, data flow, decisions made, tradeoffs, failure modes. Not a list of options. An actual design with calls made. Use when asked for "system design for", "architect this", "how should we build", or "design the backend".
cortex-integrate
Design and implement an AI feature integration — model selection, architecture pattern, system prompt, data flow, error handling, cost estimate. Use when asked to "add AI to this", "LLM integration", "add Claude/GPT", or "AI-powered feature".
spine-api
Design and spec an API — endpoints, request/response shapes, error codes, auth pattern, pagination. Applies Stripe's consistency principles. Use when asked to "design an API", "build API endpoints", "create REST API", or "API for this feature".
warden-harden
Produce a hardening spec and implement it — auth patterns, security headers, rate limiting, input validation, secrets management, dependency hygiene. Use when asked to "harden this", "add security to this service", "what security do I need", or "secure this before launch".
spine-review
API and backend code review — REST conventions, auth, validation, error handling, pagination, rate limiting, test coverage. Use when asked to "review this API", "code review", "review backend", or "pre-launch backend check".
spine-perf
Find and fix performance bottlenecks — N+1 queries, missing indexes, sync bottlenecks, caching gaps. Use when asked "why is this slow", "performance issue", "optimize this endpoint", or "N+1 queries".