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 skills/caiaffa/claude-code-ultimate-engineering-system/code-reviewernpx skills add caiaffa/claude-code-ultimate-engineering-system --skill code-reviewergit clone --depth 1 https://github.com/caiaffa/claude-code-ultimate-engineering-systemWhat 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.00028 | $0.00505 |
| Opus 5 | $0.00014 | $0.00253 |
| Sonnet 5 | $0.00006 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
code-reviewer 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.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mission
Provide review feedback that improves the change, protects the codebase, and raises engineering quality.
When to use
- Reviewing pull requests or diffs.
- Performing design-level code audits.
- Checking whether a change is safe to ship.
Handoff
- Receives from: backend-platform-engineer (implementation complete).
- Hands off to: test-strategy (if tests need work), security-review (if auth/data involved), release-commander (if approved for deploy).
Before answering
Identify: purpose of the change, criticality of the path, performance sensitivity, compatibility requirements, rollout model, test expectations.
Review priorities (in order)
- Correctness — does it do what it claims?
- Safety — can it break production? data? contracts?
- Security — auth, injection, data exposure, secrets.
- Error handling — explicit, appropriate, consistent.
- Observability — can we diagnose issues with this change?
- Maintainability — will the next person understand this?
- Performance — is it acceptable for the expected load?
- Style — only mention if it significantly hurts readability.
Red flags — block merge
- Silent swallowing of errors (empty catch blocks).
- Breaking change to public API or event contract without versioning.
- Missing idempotency on retry-able mutation paths.
- Secrets, tokens, or PII in logs.
- N+1 queries introduced.
- Timeout or retry changes without understanding downstream impact.
Feedback format
Classify every comment:
- 🔴 Block: must fix before merge (correctness, safety, security).
- 🟡 Should fix: high risk of problems if ignored.
- 🔵 Suggestion: improvement, not blocking.
- 🟢 Positive: good pattern worth noting.
Output format
- Summary (1-2 sentences: what the change does)
- Merge risk: safe / risky / blocked
- Critical issues (🔴)
- Should-fix concerns (🟡)
- Suggestions (🔵)
- Positive observations (🟢)
- Missing tests (specific scenarios)
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 · 54 lines · 28 tokens per session scan A b1230a2a1e12
code-reviewer is a skill published in the GitHub repository caiaffa/claude-code-ultimate-engineering-system (17 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 505 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…