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 skills/johnnykor82/spec-driven-planning/spec-driven-planningnpx skills add johnnykor82/spec-driven-planning --skill spec-driven-planninggit clone --depth 1 https://github.com/johnnykor82/spec-driven-planningWrote 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/johnnykor82/spec-driven-planning/spec-driven-planning)<a href="https://agentmods.dev/skills/johnnykor82/spec-driven-planning/spec-driven-planning"><img src="https://agentmods.dev/badge/skills/johnnykor82/spec-driven-planning/spec-driven-planning.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.00096 | $0.03814 |
| Opus 5 | $0.00048 | $0.01907 |
| Sonnet 5 | $0.00019 | $0.00763 |
| Haiku 4.5 | $0.00010 | $0.00381 |
Grade A, and why
spec-driven-planning 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 6d 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 — 427 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Driven Planning
Specify → Plan completely → Execute → Verify against spec. In that order. Every time.
When NOT to Use
- Simple tasks with clear, unambiguous requirements (use
planning-with-filesinstead) - Single-file changes or typo fixes
- Tasks under ~10 tool calls or 3 steps
- Quick fixes where requirements need no clarification
- When all you need is a session plan, not a project plan
Exception: If .planning/ exists, or the user references an existing spec, roadmap, or plan, use Reference Mode below even for small tasks. Do not start the full two-pass workflow unless the task changes scope, conflicts with the spec, or lacks enough plan coverage.
Relationship to spec-driven-development (skill)
This skill picks up where the spec-driven-development skill leaves off.
spec-driven-development owns the SPECIFY phase: surfacing assumptions, reframing requirements, and writing the initial spec with human review. THIS skill owns everything AFTER the spec is approved: decomposing it into a hierarchical plan, executing with compliance verification, and managing scope changes.
IF NO SPEC EXISTS when this skill loads — load spec-driven-development first and complete its Specify phase. Then return here to plan.
Key boundary:
- Before spec approval: spec is a LIVING document (
spec-driven-development) - After spec approval: spec is IMMUTABLE without explicit user instruction (this skill, via Scope Change Protocol)
FIRST: Restore Context
Before doing anything else, check for existing planning files:
ls .planning/ 2>/dev/null && echo "planning dir found" || echo "new project"
If .planning/ exists:
- Read
.planning/spec.md - Read
.planning/roadmap.md - Resolve the active path (see § Active Path below)
- Read only the plan files along the active path
- Read
.planning/progress.md(last session entry only)
Then continue from where work left off. Do NOT re-plan what is already planned.
If .planning/ does NOT exist, or spec.md is missing:
- Load the
spec-driven-developmentskill - Complete its Specify phase to create and approve the spec
- Then return here to build the plan hierarchy
What ships with it
7 files 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.
- 6d ago First seen · 427 lines · 96 tokens per session scan A ff371e772516
spec-driven-planning is a skill published in the GitHub repository johnnykor82/spec-driven-planning (2 stars, last pushed 2mo ago), licensed MIT. It adds 96 tokens to every session and 3,814 once invoked, about $0.0005 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 skills, from other repositories
codex-sdd:plan
Create design.md with technical architecture and tasks.md with executable breakdown from an approved proposal. Second phase of OpenSpec workflow.
codex-sdd:tapd-openspec-proposal
Fetch TAPD story requirements before OpenSpec proposal generation. Use when the user asks OpenSpec propose with a TAPD story URL/id, says to import TAPD requirements, or asks to generate proposal.md from TAPD.
agent-swarm
Agent skill for swarm - invoke with $agent-swarm.
babysit-babysitter-issues
This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…