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/status)<a href="https://agentmods.dev/commands/agricidaniel/ace-claude-code/status"><img src="https://agentmods.dev/badge/commands/agricidaniel/ace-claude-code/status/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/status"><img src="https://agentmods.dev/badge/commands/agricidaniel/ace-claude-code/status.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.00549 |
| Opus 5.5 | $0.00004 | $0.00220 |
| Sonnet 5.5 | $0.00002 | $0.00110 |
| Haiku 4.5 | $0.00001 | $0.00055 |
Grade A, and why
ace:status 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This is a lightweight alternative to /ace:progress - same information, faster output.
1. Quick State Check
if PROJECT.md does not exist:
Display:
[!] No project. Run /ace:new-project or /ace:init
EXIT
if ROADMAP.md does not exist:
Display:
[!] No roadmap. Run /ace:create-roadmap
EXIT
2. Compact Status Display
Read STATE.md and display:
+----------------------------------------------+
| [Project Name] |
+----------------------------------------------+
Phase: [X]/[Y] - [Phase Name]
Plan: [A]/[B] - [Plan Name]
Status: [Ready/In Progress/Complete]
[##########..........] 50%
Next: /ace:[suggested-command]
+----------------------------------------------+
3. Progress Bar Calculation
Calculate overall progress:
- Count completed phases
- Count completed plans in current phase
- Show as visual bar: [####........] XX%
Formula:
completedPhases = phases marked complete
currentPhasePlans = plans completed in current phase / total plans
overallProgress = (completedPhases + currentPhasePlans) / totalPhases * 100
4. Quick Next Action
Based on STATUS field in STATE.md:
| Status | Suggestion |
|---|---|
| needs-roadmap | /ace:create-roadmap |
| 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] |
| all-complete | Project finished! |
5. Resume File Detection
if .continue-here*.md exists:
Add to output:
[i] Resume file found - run /ace:resume-work
<success_criteria>
- Status displayed in 5 lines or less
- Progress bar shown
- Next action clearly suggested
- Executes quickly (minimal file reads) </success_criteria>
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 · 99 lines · 11 tokens per session scan A a542b5c100db
ace:status 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 549 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.
Other commands, from other repositories
fix-issue
Analyze and fix a GitHub issue.
beads-onboard
Run the interactive beads-onboard interview in the current project to generate beads conventions (AGENTS.md translation matrix, labels.md, reference.md, starter formula, pre-seeded bd remember entries).
bmad-create-story
Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]".
bmad-sprint-planning
Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan".
canvas
AI-orchestrated visual canvas production — create, populate, layout, present, generate, and export Obsidian canvases.
gpd:record-insight
Record a project-specific learning or pattern to the insights ledger.