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/insert-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.00011 | $0.00682 |
| Opus 5 | $0.00005 | $0.00341 |
| Sonnet 5 | $0.00002 | $0.00136 |
| Haiku 4.5 | $0.00001 | $0.00068 |
Grade A, and why
ace:insert-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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use for urgent work that must happen before planned phases.
Required: @.ace/planning/ROADMAP.md @.ace/planning/STATE.md
1. Validate Position
if $ARGUMENTS is empty:
Error: "Specify position: /ace:insert-phase 2"
if $ARGUMENTS > total_phases + 1:
Error: "Position [N] invalid. Roadmap has [X] phases."
2. Gather Phase Info
Use AskUserQuestion:
- "What is the goal of this urgent phase?"
- "Why must it come before Phase [N]?"
- "How many plans do you estimate?"
3. Display Impact
+==============================================================+
| INSERT PHASE IMPACT |
+==============================================================+
Current Roadmap:
Phase 1: [Name] -> stays Phase 1
Phase 2: [Name] -> becomes Phase 3
Phase 3: [Name] -> becomes Phase 4
NEW Phase 2: [New Name]
+==============================================================+
4. Get Confirmation
Use AskUserQuestion:
- "This will renumber all subsequent phases. Continue?"
- Options: "Yes, insert phase" / "Cancel"
5. Update ROADMAP.md
- Parse existing phases
- Renumber phases at and after position
- Insert new phase at position
- Update all plan IDs (02-01 becomes 03-01, etc.)
6. Update STATE.md
If current phase >= insert position:
- Increment current phase number
- Update progress calculations
7. Update Existing Plans
Rename plan files in phases/ directory:
# Example: inserting at position 2
mv phases/02-core/ phases/03-core/
mv phases/03-integration/ phases/04-integration/
Update plan IDs in each PLAN.md and SUMMARY.md file.
8. Git Commit
git add .ace/planning/
git commit -m "docs: insert phase [N] - [phase-name]
Renumbered phases [N]+ to accommodate urgent work.
"
9. Confirmation
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 · 130 lines · 11 tokens per session scan A 2ac07359a707
ace:insert-phase is a command published in the GitHub repository AgriciDaniel/ace-claude-code (24 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 682 once invoked, about $0.0001 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.