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 DollarDill/beads-superpowers --skill writing-plansgit clone --depth 1 https://github.com/DollarDill/beads-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/dollardill/beads-superpowers/writing-plans)<a href="https://agentmods.dev/skills/dollardill/beads-superpowers/writing-plans"><img src="https://agentmods.dev/badge/skills/dollardill/beads-superpowers/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/dollardill/beads-superpowers/writing-plans"><img src="https://agentmods.dev/badge/skills/dollardill/beads-superpowers/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.00021 | $0.03361 |
| Opus 5 | $0.00010 | $0.01681 |
| Sonnet 5 | $0.00004 | $0.00672 |
| Haiku 4.5 | $0.00002 | $0.00336 |
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 11d 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Plans
Overview
Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.
Assume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.
Announce at start: "I'm using the writing-plans skill to create the implementation plan."
Production-Grade Doctrine: every spec requirement MUST map to a task — a deliberate cut is surfaced as a tracked decision, never a silent omission. Never weaken, bypass, or remove a security control — a security regression is never acceptable.
Context: This should be run in a dedicated worktree (created by brainstorming skill).
Save plans to: .internal/plans/YYYY-MM-DD-<feature-name>.md
- (User preferences for plan location override this default)
Knowledge Check
Before writing tasks, query the knowledge store: bd list --label <topic> --status all + bd search "<keywords>" --status all + bd memories <keyword> (the memory half — lessons, patterns, root-causes; knowledge-beads alone miss it entirely). Then read — hits are pointers, not knowledge: bd show <id1> <id2> ... / bd recall <key> for every hit that plausibly bears on this plan. Emit KB check: N bead hits, M memory hits, K read plus a one-line disposition per read hit — folded into a task (which one) or ruled out (why).
Scope Check
If the spec covers multiple independent subsystems, it should have been broken into sub-project specs during brainstorming. If it wasn't, suggest breaking this into separate plans — one per subsystem. Each plan should produce working, testable software on its own.
File Structure
Before defining tasks, map out which files will be created or modified and what each one is responsible for. This is where decomposition decisions get locked in.
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.
- 11d ago First seen · 285 lines · 21 tokens per session scan A 4c09e40134e0
writing-plans is a skill published in the GitHub repository DollarDill/beads-superpowers (26 stars, last pushed 19d ago), licensed MIT. It adds 21 tokens to every session and 3,361 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-30.
Other skills, from other repositories
x-qdev
A compact development workflow for a small, clearly defined code change. It keeps the requirement, initially failing tests, implementation, and real verification results in one task document, following TDD, or test-driven development.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
orchestrate
A workflow manager for a full test-driven development cycle, where tests are written before implementation and code is then improved and reviewed. It coordinates planning, failing tests, implementation, refactoring, review, and committing changes.
codify-insight
A review skill that sorts lessons from completed TDD cycles into rules to keep, items to postpone, or items not to keep. TDD, or test-driven development, is a practice of writing tests around a change as part of its development cycle.
commit
A Git workflow skill that completes a TDD cycle by committing changes after required review, tests, logs, and retrospective checks pass. Git is a version-control system that records code changes and commits.
red
A test-first workflow that creates tests and confirms they fail before implementation begins. Test-driven development, or TDD, uses this failing-test stage to define the behavior that new code must provide.