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/agricidaniel/ace-claude-code/add-phasegit clone --depth 1 https://github.com/AgriciDaniel/ace-claude-codeWhat 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.00009 | $0.00397 |
| Opus 5 | $0.00005 | $0.00198 |
| Sonnet 5 | $0.00002 | $0.00079 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
ace:add-phase 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
1. Load Current Roadmap
Read ROADMAP.md to understand:
- Current phases
- Total count
- Dependencies
2. Gather Phase Info
Use AskUserQuestion:
- "What is the goal of this new phase?"
- "How many plans do you estimate?"
- "Any dependencies on other phases?"
3. Create Phase Entry
Add to ROADMAP.md:
### Phase [N+1]: [Phase Name]
**Goal:** [Description]
**Status:** Not Started
Plans:
- [ ] [phase]-01: [Plan name]
- [ ] [phase]-02: [Plan name]
Dependencies: Phase [N]
4. Update STATE.md
Update total phase count.
5. Git Commit
Commit the roadmap changes:
git add .ace/planning/ROADMAP.md
git add .ace/planning/STATE.md
git commit -m "docs: add phase [N] - [phase-name]"
6. Confirm
+==============================================================+
| PHASE ADDED |
+==============================================================+
Phase [N+1]: [Name] added to roadmap.
Total Phases: [N+1]
+==============================================================+
<success_criteria>
- New phase added to ROADMAP.md
- STATE.md updated
- Changes committed to git
- User confirmed </success_criteria>
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 · 89 lines · 9 tokens per session scan A 1d33b70cce32
ace:add-phase is a command published in the GitHub repository AgriciDaniel/ace-claude-code (24 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 397 once invoked, about $0.0000 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
canvas
AI-orchestrated visual canvas production — create, populate, layout, present, generate, and export Obsidian canvases.
document
Generate documentation for code.
review
Review code for best practices and issues.
test
Generate comprehensive tests for a file or function.
fix-issue
Analyze and fix a GitHub issue.
migrate
Create migration plan for upgrade.