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 commands/w00fx/spec-anchored-agentic-development/plan-from-issuegit clone --depth 1 https://github.com/w00fx/spec-anchored-agentic-developmentWrote 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/commands/w00fx/spec-anchored-agentic-development/plan-from-issue)<a href="https://agentmods.dev/commands/w00fx/spec-anchored-agentic-development/plan-from-issue"><img src="https://agentmods.dev/badge/commands/w00fx/spec-anchored-agentic-development/plan-from-issue.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 | $0.00010 | $0.00219 |
| Opus 5 | $0.00005 | $0.00110 |
| Sonnet 5 | $0.00002 | $0.00044 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
plan-from-issue 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 4d 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
Take the issue number from the argument. Do:
- Use
gh issue view <number>to read the full issue. - Identify the affected capability from the
stage:andarea:labels (or equivalent — adapt to your label schema). - Read that capability's AGENTS.md/CLAUDE.md.
- Read the current spec in specs///.
- Enter Plan Mode.
- Propose a phased implementation plan.
- List open questions if there's ambiguity.
Don't implement. Just plan.
This plan informs triage and issue refinement. Implementation re-plans
inside implement-feature / implement-backlog, with its own gate — do
not treat this output as the approved plan (protocol Phase 3).
Portability: this command's body works as a standalone prompt in any harness — the semantic procedure is portable; invocation, permissions, and context loading need the harness adapter.
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.
- 4d ago First seen · 24 lines · 10 tokens per session scan A d234c9c31776
plan-from-issue is a command published in the GitHub repository w00fx/spec-anchored-agentic-development (5 stars, last pushed 9d ago), licensed MIT. It adds 10 tokens to every session and 219 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-31.
Other commands, from other repositories
kiro-validate-design
Command "kiro-validate-design" from gotalab/cc-sdd, covering technical design validation, core task, execution steps, important constraints and tool guidance.
spec-intake
Execute the canonical workflow: .agent/workflows/spec-intake.md.
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
simplify
Reduce complexity without changing behavior — code simplification.
sdd-setup
Onboarding wizard — DocLanguage, Memory Bank, architecture snapshot, working agreements (quality gate, TDD working mode).
devs-team
Parallel multi-lens critique of a solution design (the active spec if present, else the decision brief). Dispatches 5 engineering lenses, merges findings, reports a verdict. Report-only, never blocks.