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/roadmapgit 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)<a href="https://agentmods.dev/commands/jonase47/ccpr/roadmap"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/roadmap.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.01502 |
| Opus 5 | $0.00000 | $0.00751 |
| Sonnet 5 | $0.00000 | $0.00300 |
| Haiku 4.5 | $0.00000 | $0.00150 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/roadmap – Create an initial roadmap
Purpose
This command creates a first roadmap based on an existing rough concept. The roadmap structures epics, milestones, and dependencies either time-based (quarters/months) or phase-based (MVP, Phase 1, Phase 2...) – selectable depending on the project character.
Execution
Step 1 – Load concept & context
Check whether the user named a concept file:
- If yes: read it completely.
- If no: search in
docs/concepts/and display a selection list:"Which concept should the roadmap be based on? [List of found concept files with title and version]"
After the selection, also read any existing decision documents
from docs/decisions/ that belong to the same project –
they contain important directional choices for planning.
Step 2 – Choose structure
Ask the user once for the desired structure if not already specified in the initial prompt:
"How should the roadmap be structured? (a) Time-based – with concrete time periods (months, quarters) (b) Phase-based – MVP, Phase 1, Phase 2 etc. without fixed dates
Tip: Time-based is suitable when deadlines or releases are known. Phase-based is better when the timeline is still open."
Wait for the answer before continuing.
Step 3 – Parallel analysis by sub-agents
Start three sub-agents in parallel using the Task tool.
All agents receive the concept, any decision documents, and the
chosen structure as context. Mark ambiguities as [UNCLEAR: ...].
Sub-Agent A – Structure epics & features
- Which epics / larger feature blocks can be derived from the concept?
- How can they be meaningfully divided into phases or time periods?
- What is MVP-critical, what is nice-to-have?
- Rough effort estimate per epic: Small / Medium / Large
Sub-Agent B – Milestones & dependencies
- Which milestones result from the epics? (e.g. "MVP live", "Multi-user active", "First feedback collected")
- Which dependencies exist between epics? (What must be done before what?)
- Are there external dependencies (decisions, tools, people)?
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 · 199 lines · 0 tokens per session scan A 9ee403eeeb55
roadmap 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,502 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.