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/refactor)<a href="https://agentmods.dev/commands/caiaffa/claude-code-ultimate-engineering-system/refactor"><img src="https://agentmods.dev/badge/commands/caiaffa/claude-code-ultimate-engineering-system/refactor/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/refactor"><img src="https://agentmods.dev/badge/commands/caiaffa/claude-code-ultimate-engineering-system/refactor.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.00016 | $0.00296 |
| Opus 5.5 | $0.00006 | $0.00118 |
| Sonnet 5.5 | $0.00003 | $0.00059 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
refactor 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
Target: $ARGUMENTS
Phase 1 — Characterize & plan (sequential)
backend-platform-engineer (safe-refactoring + test-strategy skills): current problems, behavior that must NOT change, characterization tests to write first, and a step plan where every step is independently mergeable. No structural changes yet.
Phase 2 — Challenge (sequential, decision gate)
architecture-challenger: attack the plan — accidental behavior change, hidden callers (reflection, config, other services), error-semantics drift, lost observability, steps that cannot ship incrementally. Critical findings → revise the plan.
Phase 3 — Execute (sequential)
backend-platform-engineer: one step at a time — green suite → change →
green suite. One commit per step (refactor(scope): ...). Never mix a
behavior change into a refactor commit; if one is needed, stop and report.
Phase 4 — Review (parallel)
- backend-platform-engineer (fresh instance, code-review skill) on the full diff
- security-engineer — only if auth, data access, or contracts were touched
Output
Steps executed with test output per step, preserved-behavior evidence,
remaining risks, and whether a release plan (/release) is needed.
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 · 31 lines · 16 tokens per session scan A c0684990ee83
refactor is a command published in the GitHub repository caiaffa/claude-code-ultimate-engineering-system (17 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 296 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
audio-pass
Functional audio review for implementation, mix coverage, clarity, and player feedback.
test-value-review
Use when a diff adds or changes test files, when a PR claims coverage for config, CI workflows, templates, or HTML output, or when tests look written only to satisfy a "must have tests" rule; not for Playwright selector or performance hygiene (use /playwright-review).
auditar-refactor
Invoca refactor-safety-auditor — gate canônico antes de qualquer refactor. Coleta evidências (linhas, contrato externo, coverage, mutation) e retorna veredito GO/BLOCK/WARN/GO-OVERRIDE.
quality-check-command
This command performs comprehensive code quality checks. Use it before commits or when implementation is complete.
bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
claude-loop
Use a fresh headless Claude session (Fable by default) as an independent reviewer of the whole repo, area by area (or of one branch's diff with --base), fix every real finding with regression tests, and loop until each area comes back clean twice in a row. The /codex-loop pattern on Anthropic usage. Runs autonomously.