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/remove-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.00860 |
| Opus 5 | $0.00005 | $0.00430 |
| Sonnet 5 | $0.00002 | $0.00172 |
| Haiku 4.5 | $0.00001 | $0.00086 |
Grade C, and why
ace:remove-phase scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .ace/planning/phases/{phase}/ How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use for phases that are no longer needed or should be deferred indefinitely.
Required: @.ace/planning/ROADMAP.md @.ace/planning/STATE.md
1. Validate Phase
if $ARGUMENTS is empty:
Error: "Specify phase: /ace:remove-phase 3"
if phase $ARGUMENTS not in ROADMAP.md:
Error: "Phase $ARGUMENTS not found"
if phase $ARGUMENTS is current or completed:
Warning: "Phase [N] has work. Are you sure?"
2. Check for Existing Work
if phases/{phase}/ directory exists:
List all PLAN.md and SUMMARY.md files
Show: "[X] plans exist for this phase"
3. Display Impact
+==============================================================+
| REMOVE PHASE IMPACT |
+==============================================================+
Removing: Phase [N] - [Name]
Existing work:
- [X] plans created
- [Y] plans executed
- [Z] commits made
Subsequent phases will be renumbered:
Phase [N+1] -> Phase [N]
Phase [N+2] -> Phase [N+1]
+==============================================================+
4. Get Confirmation
Use AskUserQuestion:
- "How should we handle this phase?"
- Options:
- "Archive and remove" (move to .ace/archived/)
- "Delete permanently" (no recovery)
- "Cancel"
5. Archive or Delete
If Archive:
mkdir -p .ace/archived/
mv .ace/planning/phases/{phase}/ .ace/archived/phase-{N}-{name}/
If Delete:
rm -rf .ace/planning/phases/{phase}/
6. Update ROADMAP.md
- Remove the phase entry
- Renumber subsequent phases
- Update plan IDs in remaining phases
7. Update STATE.md
If current phase > removed phase:
- Decrement current phase number
- Update progress calculations
If current phase == removed phase:
- Set to previous phase or "Phase 1 ready to plan"
8. Update Remaining Plans
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 · 165 lines · 9 tokens per session scan C 15ebf579c156
ace:remove-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 860 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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.