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/caiaffa/claude-code-ultimate-engineering-systemWrote 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/caiaffa/claude-code-ultimate-engineering-system/debug)<a href="https://agentmods.dev/commands/caiaffa/claude-code-ultimate-engineering-system/debug"><img src="https://agentmods.dev/badge/commands/caiaffa/claude-code-ultimate-engineering-system/debug/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/caiaffa/claude-code-ultimate-engineering-system/debug"><img src="https://agentmods.dev/badge/commands/caiaffa/claude-code-ultimate-engineering-system/debug.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.00020 | $0.00385 |
| Opus 5.5 | $0.00008 | $0.00154 |
| Sonnet 5.5 | $0.00004 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
debug 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.
What it actually says
Problem: $ARGUMENTS
Phase 1 — Reproduce & frame (sequential)
backend-platform-engineer (systematic-debugging skill): state the symptom precisely (observed vs expected, when it started, what changed), reproduce it (failing test or command), and list the top 3 hypotheses — each with the ONE signal that confirms or kills it. No code changes in this phase.
Phase 2 — Investigate (parallel)
- backend-platform-engineer — test the hypotheses in order, cheapest signal first, in code and tests.
- reliability-engineer — traces, metrics, logs around the window (use the Grafana MCP tools when available). If the symptom is latency/throughput, apply performance-analysis.
For an intermittent/flaky issue, reproduce with repeated runs before declaring it flaky; look for shared state, timing, ordering, real clock.
Phase 3 — Fix (sequential, decision gate)
Only after the full chain is confirmed (trigger → mechanism → symptom):
backend-platform-engineer implements the fix, a regression test for the
exact scenario, and tests for neighboring scenarios. Run the suite; paste output.
If the root cause is architectural, stop and route to /adr or /rfc.
Phase 4 — Prevent
What detection or guardrail would have caught this class earlier? Update the
relevant governance doc in ~/.claude/engineering/ if the standard has a gap.
Output
# DEBUG REPORT
Symptom / Confirmed root cause (with evidence) / Full chain
Fix (symptom-level) / Prevention (class-level) / Test output
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 · 39 lines · 20 tokens per session scan A c809008e21a3
debug is a command published in the GitHub repository caiaffa/claude-code-ultimate-engineering-system (17 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 385 once invoked, about $0.0001 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-09-15.
Other commands, from other repositories
playwright-test-heal
Run all my tests and fix the failing ones.
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
api-aqa-flow-execution-and-report-analysis
Phase 6 Execution & Report Analysis of api-aqa-flow (USER INTERACTION REQUIRED).
timeout-fix
A procedure for diagnosing and fixing tests that exceed their time limit by finding causes such as slow processing, hanging network calls, deadlocks, heavy setup, or leaked resources.
AGENTS
Run the current binary in a temporary test repository with a real PTY. Use tmux-cli when available, capture terminal output, and inspect -vv logs when behavior depends on timing or shell state. Avoid treating a piped command as proof of interactive behavior.