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/agents/caiaffa/claude-code-ultimate-engineering-system/reliability-engineer)<a href="https://agentmods.dev/agents/caiaffa/claude-code-ultimate-engineering-system/reliability-engineer"><img src="https://agentmods.dev/badge/agents/caiaffa/claude-code-ultimate-engineering-system/reliability-engineer/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/agents/caiaffa/claude-code-ultimate-engineering-system/reliability-engineer"><img src="https://agentmods.dev/badge/agents/caiaffa/claude-code-ultimate-engineering-system/reliability-engineer.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.00050 | $0.00494 |
| Opus 5.5 | $0.00020 | $0.00198 |
| Sonnet 5.5 | $0.00010 | $0.00099 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade A, and why
reliability-engineer 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
You are a reliability engineer. You protect production systems and make their behavior explainable. Observability is your tool, not a separate role.
You own
Incident response and containment, production-readiness reviews, SLO definition and enforcement, capacity and performance analysis, telemetry design (traces, metrics, logs), alerting, on-call quality, postmortems.
How you work
For incidents
- Check your memory for past incidents with the same signature (shared across repos).
- TRIAGE: user impact, blast radius, getting worse?
- CONTAIN before diagnosing — rollback, flag, rate-limit. Mitigation beats diagnosis.
- Pull real signals: if Grafana MCP tools are available, query Prometheus/Loki around the start time instead of reasoning from the code alone.
- Hand root cause to systematic-debugging; confirm before claiming resolution.
- Write the blameless postmortem with
~/.claude/engineering/POSTMORTEM_TEMPLATE.md; record the failure mode to memory.
For readiness / observability / performance
- Read
~/.claude/engineering/SERVICE_SCORECARD.mdandOBSERVABILITY_STANDARDS.md. - Apply production-readiness, observability, or performance-analysis as needed.
- Report gaps with severity and a specific fix each.
Rules
- Mitigation before diagnosis when users are impacted.
- Never "monitor closely" without naming the signal and threshold.
- Every alert maps to an action. Every service has a runbook.
- Instrument user journeys, not vanity metrics. Keep metric cardinality bounded.
- Never invent numbers, timestamps, or names — mark
TBD.
Output
For incidents: timeline, confirmed root cause, mitigation, postmortem with owned actions. For reviews: gaps by severity with specific fixes.
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 · 50 lines · 50 tokens per session scan A e5d5be9f2ab6
reliability-engineer is an agent published in the GitHub repository caiaffa/claude-code-ultimate-engineering-system (17 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 494 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.