plan

A command that turns an approved proposal into implementation instructions in task and, when needed, design files. It writes the instructions so an agent without the earlier conversation can use them.

In plain words
What is it for?
Use it to create a task list, add design details for larger changes, and validate the handoff before implementation.
Why use it?
It removes ambiguity before coding and checks that the resulting handoff contains enough information to continue.

Command

Install

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.

agentmods
npx agentmods add commands/ribeirogab/specwright/plan
Clone the repo
git clone --depth 1 https://github.com/ribeirogab/specwright
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 120 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00041 $0.00120
Opus 5 $0.00020 $0.00060
Sonnet 5 $0.00008 $0.00024
Haiku 4.5 $0.00004 $0.00012

Measured yesterday against content hash 57554f660b29, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 yesterday.

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.

plugins/sw/commands/plan.md · 9 lines

What it actually says

plan — the technical plan, written for a stranger

Run the specwright plan skill. Read ${CLAUDE_PLUGIN_ROOT}/skills/plan/SKILL.md and follow its instructions exactly, treating $ARGUMENTS as the skill's input.

Changes

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.

  1. yesterday First seen · 9 lines · 41 tokens per session scan A 57554f660b29

Subscribe to this mod's changes

plan is a command published in the GitHub repository ribeirogab/specwright (3 stars, last pushed 24d ago), licensed MIT. It adds 41 tokens to every session and 120 once invoked, about $0.0002 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.