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.
git clone --depth 1 https://github.com/AgriciDaniel/ace-claude-codeWrote 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/agricidaniel/ace-claude-code/create-roadmap)<a href="https://agentmods.dev/commands/agricidaniel/ace-claude-code/create-roadmap"><img src="https://agentmods.dev/badge/commands/agricidaniel/ace-claude-code/create-roadmap/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/agricidaniel/ace-claude-code/create-roadmap"><img src="https://agentmods.dev/badge/commands/agricidaniel/ace-claude-code/create-roadmap.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.00013 | $0.00644 |
| Opus 5.5 | $0.00005 | $0.00258 |
| Sonnet 5.5 | $0.00003 | $0.00129 |
| Haiku 4.5 | $0.00001 | $0.00064 |
Grade A, and why
ace:create-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 1mo 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This establishes the phase sequence and enables progress tracking.
Load templates: @.ace/templates/planning/roadmap.md @.ace/templates/planning/state.md
Optional context: @.ace/planning/codebase/ (if brownfield)
1. Verify Prerequisites
if PROJECT.md does not exist:
Error: "Run /ace:new-project first"
2. Read Project Requirements
Parse PROJECT.md to understand:
- Core value
- Must-have requirements
- Technical stack
- Constraints
3. Propose Phases
Based on requirements, propose 3-6 phases:
+==============================================================+
| PROPOSED ROADMAP |
+==============================================================+
Phase 1: Foundation
- Set up project structure
- Configure tooling
- Basic scaffolding
Phase 2: Core Features
- [Based on must-haves]
- [Primary functionality]
Phase 3: Integration
- Connect components
- Polish UI
- Testing
[Additional phases if needed]
+==============================================================+
4. Get Approval
Use AskUserQuestion:
- "Does this phase breakdown work for you?"
- Options: "Yes, create roadmap" / "Adjust phases"
If adjust:
- Ask what changes needed
- Revise and re-present
5. Create ROADMAP.md
Write to .ace/planning/ROADMAP.md:
- Phase definitions with goals
- Empty plan slots
- Dependencies between phases
6. Initialize STATE.md
Write to .ace/planning/STATE.md:
- Reference PROJECT.md
- Set position to "Phase 1 ready to plan"
- Initialize empty metrics
- Set session start time
7. Git Commit (if enabled)
git add .ace/planning/
git commit -m "docs: initialize [project-name] ([N] phases)
[One-liner from PROJECT.md]
Phases:
1. [phase-name]: [goal]
2. [phase-name]: [goal]
3. [phase-name]: [goal]
"
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.
- 1mo ago First seen · 139 lines · 13 tokens per session scan A e88adec0eefa
ace:create-roadmap is a command published in the GitHub repository AgriciDaniel/ace-claude-code (27 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 644 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-30.