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/show-plan)<a href="https://agentmods.dev/commands/agricidaniel/ace-claude-code/show-plan"><img src="https://agentmods.dev/badge/commands/agricidaniel/ace-claude-code/show-plan/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/show-plan"><img src="https://agentmods.dev/badge/commands/agricidaniel/ace-claude-code/show-plan.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.00010 | $0.01208 |
| Opus 5.5 | $0.00004 | $0.00483 |
| Sonnet 5.5 | $0.00002 | $0.00242 |
| Haiku 4.5 | $0.00001 | $0.00121 |
Grade A, and why
ace:show-plan 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This is a read-only inspection command for reviewing plans before execution.
Required: @.ace/planning/STATE.md
Load plan from:
- If $ARGUMENTS is a path: Use that path directly
- If $ARGUMENTS is a plan_id (e.g., "02-01"): Find in phases/
- If no arguments: Read STATE.md for current plan reference
1. Locate Plan
if $ARGUMENTS provided:
if $ARGUMENTS is path (contains /):
plan_path = $ARGUMENTS
else:
# Treat as plan_id like "02-01"
Find matching PLAN.md in .ace/planning/phases/
if no $ARGUMENTS:
Read STATE.md for current plan path
if no current plan:
Error: "No current plan. Run /ace:plan-phase [N] first"
2. Parse Plan File
Read PLAN.md and extract:
- Phase and plan metadata
- Tasks (max 3)
- Zone assignments per task
- File patterns per task
- Checkpoints (if any)
- Verification criteria
3. Display Plan Header
+==============================================================+
| ACE PLAN |
+==============================================================+
| Phase: [X] - [Phase Name] |
| Plan: [plan_id] - [Plan Name] |
| Status: [Ready to execute / In progress / Complete] |
| Created: [date] |
+==============================================================+
Goal: "[Plan objective from PLAN.md]"
+==============================================================+
4. Display Visual Task Distribution
TASK DISTRIBUTION:
"[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 |
| - a.ts | | - b.ts | | - c.ts |
+--------+ +--------+ +--------+
+==============================================================+
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 · 213 lines · 10 tokens per session scan A de17b86e3e04
ace:show-plan is a command published in the GitHub repository AgriciDaniel/ace-claude-code (27 stars, last pushed 6mo ago), licensed MIT. It adds 10 tokens to every session and 1,208 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.