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/spumer/i-m-senior-developer/plan-roadmapgit clone --depth 1 https://github.com/spumer/i-m-senior-developerWhat 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.00035 | $0.00462 |
| Opus 5 | $0.00017 | $0.00231 |
| Sonnet 5 | $0.00007 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
plan-roadmap 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.
What it actually says
Активируй скилл product-discovery с видом документа roadmap и выполни его порядок работы от начала до конца. Для этого вида скилл загружает references/roadmap-mode.md.
Разбор $ARGUMENTS:
- Путь к
EPIC.md— порядок живёт в том же каталоге: целевой файлROADMAP.mdрядом с гипотезой. - Путь к каталогу гипотезы — возьми
EPIC.mdиз него; если файла нет — остановись и попроси путь к гипотезе. - Пустой аргумент — остановись и попроси путь к гипотезе: порядок без владельца результата не строится.
allocate для порядка не вызывается: имя файла фиксированное, номера выдачи нет. Родительская гипотеза передаётся в validate-target и sync флагом --parent — она обязана лежать в том же каталоге.
Значимые решения задавай через AskUserQuestion по протоколу скилла.
Успешный запуск всегда записывает результат в epics/EPIC-NNNN-<slug>/ROADMAP.md. После успешной записи в чате — только короткий итог по формату скилла: вид, путь и версия, два–четыре главных исхода, следующая команда, когда она есть. Следующую команду не выполняй сам. Полный документ в чат не дублируется.
Правила горизонтов, условия перехода и проверка готовности — в скилле; не повторяй их здесь. При ошибке записи следуй разделу «Ошибка записи» скилла: подготовленное тело документа — запасной результат.
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 First seen · 23 lines · 35 tokens per session scan A 1bd9c4ef9ebf
plan-roadmap is a command published in the GitHub repository spumer/i-m-senior-developer (11 stars, last pushed 11d ago), licensed MIT. It adds 35 tokens to every session and 462 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.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
speckit.auto
Automatically execute the four core phases of the Spec-Driven Development (SDD) pipeline: specify → plan → tasks → implement, in strict sequential order.
daily-priorities
Query DIGI Jira via the Atlassian MCP to build a prioritized daily work plan. The report has two parts: suggested priorities (the recommendation) and full context (everything you need to evaluate whether the suggestions are right and what else is on the docket).
OPSX: Bulk Archive
Archive multiple completed changes at once.
sync-linear
Sync current work with Linear ticket status.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).