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/verify-work)<a href="https://agentmods.dev/commands/agricidaniel/ace-claude-code/verify-work"><img src="https://agentmods.dev/badge/commands/agricidaniel/ace-claude-code/verify-work/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/verify-work"><img src="https://agentmods.dev/badge/commands/agricidaniel/ace-claude-code/verify-work.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.00683 |
| Opus 5.5 | $0.00004 | $0.00273 |
| Sonnet 5.5 | $0.00002 | $0.00137 |
| Haiku 4.5 | $0.00001 | $0.00068 |
Grade A, and why
ace:verify-work 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Captures issues for fix planning if needed.
Required: @.ace/planning/STATE.md
Load: Latest SUMMARY.md from phases/
1. Load Completed Work
Find most recent SUMMARY.md or use $ARGUMENTS.
Display what was built:
+==============================================================+
| VERIFY WORK |
+==============================================================+
Plan: [plan_id] - [plan name]
Completed: [date]
Files Created/Modified:
- src/models/user.ts
- src/services/auth.ts
- src/routes/auth.ts
+==============================================================+
2. Verification Checklist
Present from PLAN.md verification criteria:
VERIFICATION CHECKLIST:
Task 1: [Task Name]
- [ ] [Verification step 1]
- [ ] [Verification step 2]
Task 2: [Task Name]
- [ ] [Verification step 1]
Task 3: [Task Name]
- [ ] [Verification step 1]
- [ ] [Verification step 2]
+==============================================================+
3. Guide Testing
SUGGESTED TESTS:
1. Start the application:
npm run dev
2. Test [Feature 1]:
[How to test]
3. Test [Feature 2]:
[How to test]
+==============================================================+
4. Collect Feedback
Use AskUserQuestion:
"Did everything work as expected?" Options:
- "Yes, all good" -> Mark verified, continue
- "Found issues" -> Capture issues
If issues found: "Describe the issues you found:" [Free text capture]
5. Handle Results
All Good
+==============================================================+
| VERIFICATION PASSED |
+==============================================================+
Plan [plan_id] verified successfully.
Next:
- /ace:plan-phase [N] Continue development
- /ace:progress Check overall status
+==============================================================+
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 · 160 lines · 11 tokens per session scan A 3734243386f8
ace:verify-work 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 683 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
test
Generate comprehensive tests for a file or function.
cloudflare-durable-objects:setup
Interactive Durable Objects project initialization. Scaffolds new DO project with proper bindings, migrations, and boilerplate code.
cloudflare-workers:test-setup
Interactive Vitest setup wizard for Cloudflare Workers testing. Configures @cloudflare/vitest-pool-workers, mocks bindings, and creates example tests.
check
Run the abap2UI5 gates (abaplint and the abap2UI5 linter) over the project or the changed classes, explain every finding and fix the ones that are clearly safe.
pr-ready
Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.
verify-setup
One-time setup for /verify and /break: sniff boot/seed/health, confirm, write .verify/setup.json and the app profile.