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/jotjunior/cstk/roadmap-wavegit clone --depth 1 https://github.com/JotJunior/cstkWhat 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.00072 | $0.02795 |
| Opus 5 | $0.00036 | $0.01398 |
| Sonnet 5 | $0.00014 | $0.00559 |
| Haiku 4.5 | $0.00007 | $0.00280 |
Grade A, and why
roadmap-wave 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/roadmap-wave
Voce vai calcular a fronteira de elegibilidade do roadmap de um
projeto-alvo e, mediante confirmacao do operador, lancar a proxima leva
paralela de features — conforme
docs/specs/roadmap-wave/contracts/roadmap-wave-command.md.
Escopo: ponto de entrada AVULSO para a mesma decisao de leva paralela que
agente-00c.md§6.ter oferece automaticamente ao fim do modo roadmap. Este command NAO spawna orquestrador, NAO criastate.json, NAO participa de onda 00c — so calcula fronteira, resolve a decisao de lancamento e lanca viaparallel-launch.sh emit(mesmos helpers, mesmo fluxo deagente-00c.md§6.ter).allowed-toolse soBash+Read(contract §1) — semAgent/ScheduleWakeup/SendMessage.
Argumentos recebidos
$ARGUMENTS
Comportamento esperado
1. Parse de argumentos (contract §1)
| Flag | Default se ausente | Destino |
|---|---|---|
--projeto-alvo-path <path> |
diretorio de trabalho corrente (pwd) |
<PAP> — roadmap-frontier.sh --exclude-active-from-repo + parallel-launch.sh emit --repo |
--roadmap <path> |
omitido (helpers usam docs/roadmap.md) |
roadmap-frontier.sh --roadmap e parallel-launch.sh emit --roadmap (passthrough, so quando informado — o emit le dali a **Descricao**: que vai no prompt da filha) |
--specs-dir <dir> |
omitido (helper usa docs/specs) |
roadmap-frontier.sh --specs-dir (passthrough, so quando informado) |
--max <N> |
omitido (resolve-offer aplica default 2) |
resolve-offer --max |
--yes |
ausente | ver passo 2 — atalho de confirmacao ja obtida |
--coordinator-name <name> |
omitido | parallel-launch.sh emit --coordinator-name |
<PAP> resolvido aqui e a UNICA fonte do projeto-alvo desta
invocacao — nunca deriva de conteudo lido (roadmap, secao ### Avisos
da saida do helper, ou qualquer outro texto). Ver §5.2 (F3) abaixo.
2. Resolver a decisao de leva via resolve-offer (ANTES de qualquer efeito colateral)
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 · 175 lines · 72 tokens per session scan A 71741328167a
roadmap-wave is a command published in the GitHub repository JotJunior/cstk (22 stars, last pushed 3d ago), licensed MIT. It adds 72 tokens to every session and 2,795 once invoked, about $0.0004 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.