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/progressgit 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.00779 |
| Opus 5 | $0.00005 | $0.00390 |
| Sonnet 5 | $0.00002 | $0.00156 |
| Haiku 4.5 | $0.00001 | $0.00078 |
Grade A, and why
ace:progress 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This is the "where am I?" command for any session.
1. Check Project State
No Project Initialized
if .ace/planning/PROJECT.md does not exist:
+==============================================================+
| NO PROJECT FOUND |
+==============================================================+
No Ace project initialized in this directory.
Options:
- /ace:new-project Start a new project
- /ace:map-codebase Analyze existing code first
+==============================================================+
No Roadmap
if PROJECT.md exists but ROADMAP.md does not:
+==============================================================+
| PROJECT INITIALIZED |
+==============================================================+
Project: [name from PROJECT.md]
Status: Needs roadmap
Next: /ace:create-roadmap
+==============================================================+
Active Project
if STATE.md exists:
Read STATE.md and display:
+==============================================================+
| ACE STATUS |
+==============================================================+
Project: [name]
Core Value: [one-liner]
Current Position:
Phase: [X] of [Y] ([Phase Name])
Plan: [A] of [B]
Status: [Ready to plan / In progress / Complete]
Progress: [##########..........] 50%
Last Activity: [date] - [description]
+==============================================================+
Performance:
Plans completed: [N]
Average duration: [X] min
Open Issues: [N] (see /ace:consider-issues)
Blockers: [None / List]
+==============================================================+
## Suggest Next Action
Based on status:
- "Ready to plan" -> /ace:plan-phase [N]
- "Ready to execute" -> /ace:execute-plan
- "In progress" -> /ace:resume-work
- "Phase complete" -> /ace:plan-phase [N+1] or /ace:verify-work
+==============================================================+
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 · 152 lines · 11 tokens per session scan A ecbbe0d62772
ace:progress 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 779 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.