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/jonase47/ccpr/roadmap-updategit clone --depth 1 https://github.com/jonase47/ccprWrote 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/jonase47/ccpr/roadmap-update)<a href="https://agentmods.dev/commands/jonase47/ccpr/roadmap-update"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/roadmap-update.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.1 | $0.00000 | $0.01322 |
| Opus 5 | $0.00000 | $0.00661 |
| Sonnet 5 | $0.00000 | $0.00264 |
| Haiku 4.5 | $0.00000 | $0.00132 |
Grade A, and why
roadmap-update 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/roadmap-update – Update an existing roadmap
Purpose
This command updates an existing roadmap based on new findings, completed milestones, changed priorities, or new decisions. Each revision is versioned and timestamped with date + time.
Execution
Step 1 – Load roadmap & context
Check whether the user named a roadmap file:
- If yes: read it completely.
- If no: search in
docs/roadmaps/and display a selection list:"Which roadmap should be updated? [List of found files with title and current version]"
Additionally read newer concept or decision documents that were created after the roadmap's creation date – they might contain relevant changes.
Step 2 – Clarify reason for change & context
Check whether the user has described what has changed.
If not sufficiently described, ask once:
"What has changed or should be re-evaluated? (e.g. epic completed, priority shifted, new requirement, timeline adjusted, new decision made)"
If an input file with new notes or decisions was named: read it as well.
Step 3 – Parallel analysis by sub-agents
Start three sub-agents in parallel using the Task tool.
All agents receive the existing roadmap and the change context.
Mark ambiguities as [UNCLEAR: ...].
Sub-Agent A – What changes in epics & timeline?
- Which epics or phases are affected by the change?
- Do epics need to be shifted, split, added, or removed?
- Does the structure (time-based/phase-based) need to be adjusted?
- Status updates: What is newly "In Progress" or "Done"?
Sub-Agent B – Impact on milestones & dependencies
- Which milestones shift or are dropped?
- Do new dependencies arise from the change?
- Which existing dependencies are thereby resolved?
- Are there domino effects on subsequent epics?
Sub-Agent C – Impact on risks & critical path
- Does the critical path change?
- Do new risks arise, do any fall away?
- Is new buffer needed at specific points?
- What jeopardizes the updated planning?
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 · 161 lines · 0 tokens per session scan A 72973756de04
roadmap-update is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,322 tokens. 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-09-03.
Other commands, from other repositories
sdd-implement
Execute a task list in dependency order, tests before implementation for each task, halting on any non-parallel failure instead of pressing ahead.
wiki-tune
Tune wiki schema and conventions interactively.
experiment
Design A/B test with statistical rigor. Usage: /mindforge:experiment [feature] [--metric conversion|engagement|revenue] [--duration 2w].
pseo-init
Use when: kullanıcı "yeni proje", "init", "proje kur", "yeni domain ekle", "scaffold" gibi ifadeler kullanır ya da /pseo-init çağırırsa. Also use when: portföye yeni bir SEO projesi alındı, projects/{slug}/ klasörü ve project.config.json dosyasının schemaya uygun ilk hâli üretilecek; brief'te slug + domain + market…
forge-insights
Analyze past sessions for error patterns, file activity, and recommendations.
forge-context-status
Report on current context window usage, cache health, and compaction recommendation. Read-only — does not compact.