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/resume-taskgit 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.00010 | $0.00445 |
| Opus 5 | $0.00005 | $0.00222 |
| Sonnet 5 | $0.00002 | $0.00089 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
ace:resume-task 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.
What it actually says
Used when execution stopped mid-task (not between tasks).
Required: @.ace/planning/STATE.md PLAN.md for the specified plan
1. Parse Task ID
if $ARGUMENTS is empty or invalid format:
Error: "Specify task: /ace:resume-task 01-02-1"
Extract: phase, plan, task number
2. Load Task Context
Read PLAN.md for that task:
- Task description
- Zone assignment
- Files involved
- Verification criteria
3. Check Git State
git status --porcelain
git log --oneline -5
Determine:
- What commits exist for this plan
- What files have uncommitted changes
- What work was already done
4. Display Resume Context
+==============================================================+
| RESUME TASK |
+==============================================================+
Task: [task_id] - [task name]
Zone: [ALPHA/BETA/GAMMA]
Previous Work:
- [Files already created/modified]
- [Commits already made]
Remaining:
- [What still needs to be done]
+==============================================================+
5. Resume Execution
Spawn Team Lead for just this task:
- Provide context of what's already done
- Complete remaining work
- Commit when done
6. Update State
After completion:
- Update STATE.md
- Continue with remaining tasks if any
<success_criteria>
- Task context loaded
- Previous work identified
- Task completed
- Properly committed </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.
- 2d ago First seen · 99 lines · 10 tokens per session scan A 6efabc488c7d
ace:resume-task is a command published in the GitHub repository AgriciDaniel/ace-claude-code (24 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 445 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.
test
Generate comprehensive tests for a file or function.
review
Review code for best practices and issues.
fix-issue
Analyze and fix a GitHub issue.
migrate
Create migration plan for upgrade.