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/plan-phase)<a href="https://agentmods.dev/commands/agricidaniel/ace-claude-code/plan-phase"><img src="https://agentmods.dev/badge/commands/agricidaniel/ace-claude-code/plan-phase/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/plan-phase"><img src="https://agentmods.dev/badge/commands/agricidaniel/ace-claude-code/plan-phase.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.00011 | $0.01012 |
| Opus 5.5 | $0.00004 | $0.00405 |
| Sonnet 5.5 | $0.00002 | $0.00202 |
| Haiku 4.5 | $0.00001 | $0.00101 |
Grade A, and why
ace:plan-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 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Each task is assigned to a zone (ALPHA/BETA/GAMMA) for parallel execution.
Required: @.ace/planning/STATE.md @.ace/planning/PROJECT.md @.ace/planning/ROADMAP.md
Load: @.ace/config.json (for project type) @.ace/project-types.json (for zone definitions)
Optional: @.ace/planning/codebase/ (if exists) @.ace/planning/ISSUES.md (for deferred items to address)
Template: @.ace/templates/planning/plan.md
1. Validate Phase Number
if $ARGUMENTS is empty:
Error: "Specify phase number: /ace:plan-phase 1"
if phase $ARGUMENTS not in ROADMAP.md:
Error: "Phase $ARGUMENTS not found in ROADMAP.md"
2. Load Context
Read and understand:
- Current phase goal from ROADMAP.md
- Project requirements from PROJECT.md
- Current state from STATE.md
- Project type and zone definitions
- Any open issues to potentially address
3. Determine Plan Number
count existing plans in .ace/planning/phases/{phase}/
next_plan = count + 1
plan_id = "{phase:02d}-{next_plan:02d}"
4. Design Tasks
Create maximum 3 tasks based on:
- Phase goal
- Zone ownership (project-types.json)
- Dependencies between tasks
Each task must:
- Be assigned to exactly one zone
- Have clear file scope
- Be independently committable
- Have verification criteria
5. Display Visual Plan
+==============================================================+
| ACE PLAN |
+==============================================================+
| Phase: [X] - [Phase Name] |
| Plan: [Y] of [estimated] |
+==============================================================+
"[Phase Goal]"
|
+---------------+---------------+
| | |
v v v
+--------+ +--------+ +--------+
| ALPHA | | BETA | | GAMMA |
+--------+ +--------+ +--------+
| Task 1 | | Task 2 | | Task 3 |
| [desc] | | [desc] | | [desc] |
+--------+ +--------+ +--------+
| Files: | | Files: | | Files: |
| - x.ts | | - y.ts | | - z.ts |
+--------+ +--------+ +--------+
+==============================================================+
| Execution: PARALLEL (3 Team Leads) |
| Estimated commits: 4 (3 tasks + 1 docs) |
+==============================================================+
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 · 168 lines · 11 tokens per session scan A 290fdacb418d
ace:plan-phase is a command published in the GitHub repository AgriciDaniel/ace-claude-code (27 stars, last pushed 6mo ago), licensed MIT. It adds 11 tokens to every session and 1,012 once invoked, about $0.0000 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.