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/plan-fix)<a href="https://agentmods.dev/commands/agricidaniel/ace-claude-code/plan-fix"><img src="https://agentmods.dev/badge/commands/agricidaniel/ace-claude-code/plan-fix/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/plan-fix"><img src="https://agentmods.dev/badge/commands/agricidaniel/ace-claude-code/plan-fix.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.00012 | $0.01473 |
| Opus 5.5 | $0.00005 | $0.00589 |
| Sonnet 5.5 | $0.00002 | $0.00295 |
| Haiku 4.5 | $0.00001 | $0.00147 |
Grade A, and why
ace:plan-fix 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Load: Related PLAN.md and SUMMARY.md
1. Load and Parse Issues
Read UAT-ISSUES.md or the specified issues file. Each issue entry follows this structure:
### ISS-XXX: [Title]
- **Type:** Bug | Regression | Missing Feature | Integration Failure
- **Severity:** Critical | High | Medium | Low
- **Source:** UAT test name or verification step
- **Affected Files:** List of files involved
- **Description:** What went wrong
- **Expected:** What should have happened
- **Actual:** What actually happened
Parse each issue and extract the key metadata for analysis.
2. Analyze Issues and Determine Zone Ownership
For each issue, determine which zone should own the fix:
Zone Assignment Rules:
| Issue Characteristics | Assigned Zone |
|---|---|
| Core logic, algorithms, main entry points | ALPHA |
| UI components, user interactions, display | BETA |
| Data layer, API calls, external integrations | GAMMA |
| Cross-cutting (affects multiple zones) | ALPHA (coordinates) |
| Build/config issues | Orchestrator handles directly |
Analysis checklist per issue:
- Identify the root cause file(s)
- Check which zone originally created the affected code
- Estimate fix complexity (Simple: < 30 min, Medium: 30-90 min, Complex: > 90 min)
- Identify dependencies (does this fix require other fixes first?)
- Check for regression risk (will fixing this break other things?)
3. Convert Issues to Fix Tasks
Transform each issue into a structured task. The issue-to-task mapping follows this pattern:
Issue-to-Task Mapping Examples:
| Issue | Resulting Task |
|---|---|
ISS-001: Login button not responding |
BETA-FIX-001: Restore click handler on login button component |
ISS-002: API returns 500 on /users endpoint |
GAMMA-FIX-001: Fix error handling in users API controller |
ISS-003: Calculation produces NaN for negative inputs |
ALPHA-FIX-001: Add input validation to calculation engine |
ISS-004: Modal doesn't close on ESC key |
BETA-FIX-002: Add keyboard event listener to modal component |
ISS-005: Cache not invalidating on update |
GAMMA-FIX-002: Implement cache invalidation in data service |
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 · 200 lines · 12 tokens per session scan A 863010ec96be
ace:plan-fix is a command published in the GitHub repository AgriciDaniel/ace-claude-code (27 stars, last pushed 6mo ago), licensed MIT. It adds 12 tokens to every session and 1,473 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
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.
break
Try to break a change on a disposable local stack: restarts, races, dependency failures, shipped defaults, users acting out of order.
test
Generate comprehensive tests for a file or function.
bmad-qa-generate-e2e-tests
Generate end to end automated tests for existing features. Use when the user says "create qa automated tests for [feature]".
add-e2e-test
Scaffold a Playwright end-to-end test with FrameLocator for embedded Shopify app testing.