Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add spumer/i-m-senior-developer/plugin install plannerWrote 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/spumer/i-m-senior-developer/plan-do)<a href="https://agentmods.dev/commands/spumer/i-m-senior-developer/plan-do"><img src="https://agentmods.dev/badge/commands/spumer/i-m-senior-developer/plan-do/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/commands/spumer/i-m-senior-developer/plan-do"><img src="https://agentmods.dev/badge/commands/spumer/i-m-senior-developer/plan-do.svg" alt="Reviewed on agentmods" width="80" 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.00014 | $0.05129 |
| Opus 5.5 | $0.00006 | $0.02052 |
| Sonnet 5.5 | $0.00003 | $0.01026 |
| Haiku 4.5 | $0.00001 | $0.00513 |
Grade A, and why
plan-do 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 2d 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Задача
Выполни план реализации для: $ARGUMENTS
1. Разреши файлы плана
Определи каталог фичи по переданному каталогу или файлу. Актуальный план выполнения — PLANNER_EXECUTION.md в этом каталоге. После проверки сохрани канонические абсолютные пути как feature_directory, execution_path и architecture_path.
Не запускай ни одного агента, если:
- аргумент не указывает на читаемый путь;
PLANNER_EXECUTION.mdотсутствует или недоступен для чтения;- заголовок плана не указывает на читаемый архитектурный документ;
- пути архитектуры и плана совпадают.
Если плана выполнения нет, сообщи человеку точную команду:
/planner:plan <путь-к-архитектуре>
Не считай старый PLANNER_OUTPUT.md актуальным планом выполнения.
2. Разреши проектный контекст до работы
После успешной проверки каталога фичи, плана и архитектуры вызови помощник состояния:
python3 "${CLAUDE_PLUGIN_ROOT}/skills/planner/assets/plan_state.py" \
resolve-context
Интерпретируй код завершения:
-
0— сохрани полеpathиз JSON какplanner_context_path. Это единственный путь, по которому команда читает контекст проекта; -
3— не запускай ни одного рабочего вызова. Покажи человекуstatus, каждый путь изsearchedв порядке проверки и точную команду восстановления:/planner:plan <разрешённый-путь-к-архитектуре> -
64— вызов помощника составлен неверно; исправь его и повтори разрешение до любого рабочего вызова.
Проверка не создаёт и не изменяет контекст. При коде 3 не сканируй проект и не выбирай роль вместо остановки.
3. Проверяй свежесть перед каждым вызовом агента
Перед каждым рабочим вызовом агента запускай помощник состояния:
python3 "${CLAUDE_PLUGIN_ROOT}/skills/planner/assets/plan_state.py" check <путь-к-PLANNER_EXECUTION.md>
Интерпретируй код завершения:
0— план актуален, можно продолжать;2— план устарел, остановись до вызова агента;3— план недействителен или нечитаем, остановись до вызова агента;64— вызов помощника составлен неверно; исправь его и повтори проверку до вызова агента.
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.
- 2d ago Changed · +25 lines 063361b4e27d
- 1mo ago Changed · +22 lines f6b7cca142d9
- 1mo ago First seen · 188 lines · 14 tokens per session scan A a7500c3a8dfb
plan-do is a command published in the GitHub repository spumer/i-m-senior-developer (11 stars, last pushed 3d ago), licensed MIT. It adds 14 tokens to every session and 5,129 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-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.