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/list-phases)<a href="https://agentmods.dev/commands/agricidaniel/ace-claude-code/list-phases"><img src="https://agentmods.dev/badge/commands/agricidaniel/ace-claude-code/list-phases/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/list-phases"><img src="https://agentmods.dev/badge/commands/agricidaniel/ace-claude-code/list-phases.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.00014 | $0.01004 |
| Opus 5.5 | $0.00006 | $0.00402 |
| Sonnet 5.5 | $0.00003 | $0.00201 |
| Haiku 4.5 | $0.00001 | $0.00100 |
Grade A, and why
ace:list-phases 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This is the "big picture" command for understanding project structure.
Optional: @.ace/planning/PROJECT.md (for project name)
1. Check Project Exists
if .ace/planning/ROADMAP.md does not exist:
+==============================================================+
| NO ROADMAP FOUND |
+==============================================================+
No roadmap exists for this project.
Options:
- /ace:new-project Start a new project
- /ace:create-roadmap Create roadmap (if PROJECT.md exists)
+==============================================================+
2. Load Phase Data
Read ROADMAP.md and STATE.md to extract:
- All phases with names and goals
- Status of each phase (Not Started / In Progress / Complete)
- Plans completed vs total per phase
- Dependencies between phases
- Current phase indicator
3. Display Phase Overview
+==============================================================+
| PROJECT PHASES |
+==============================================================+
| Project: [Name from PROJECT.md] |
| Total Phases: [N] |
| Overall Progress: [##########..........] 50% |
+==============================================================+
PHASE OVERVIEW:
| # | Phase Name | Status | Plans | Deps |
|---|------------------|--------------|----------|---------|
| 1 | [Foundation] | [Complete] | 2/2 [**] | None |
| 2 | [Core Features] | [In Progress]| 1/3 [*-] | 1 |
| 3 | [Integration] | [Not Started]| 0/2 [--] | 2 |
| 4 | [Polish] | [Not Started]| 0/1 [-] | 3 |
Legend: [*] = Complete, [-] = Pending
+==============================================================+
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 · 166 lines · 14 tokens per session scan A 2d1a2c10f8d4
ace:list-phases is a command published in the GitHub repository AgriciDaniel/ace-claude-code (27 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 1,004 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.