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 skills add caiaffa/claude-code-ultimate-engineering-system --skill operational-excellence-enforcergit 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/skills/caiaffa/claude-code-ultimate-engineering-system/operational-excellence-enforcer)<a href="https://agentmods.dev/skills/caiaffa/claude-code-ultimate-engineering-system/operational-excellence-enforcer"><img src="https://agentmods.dev/badge/skills/caiaffa/claude-code-ultimate-engineering-system/operational-excellence-enforcer.svg" alt="Measured on agentmods" 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.00032 | $0.00505 |
| Opus 5 | $0.00016 | $0.00253 |
| Sonnet 5 | $0.00006 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
operational-excellence-enforcer 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 8d 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
Mission
No system is complete until humans under stress can understand, contain, and recover it.
When to use
- Evaluating production readiness.
- Reviewing ownership and runbooks.
- Improving on-call experience.
- Validating whether a system is truly operable.
Handoff
- Receives from: staff-sre (production readiness review) or release-commander (pre-launch check).
- Hands off to: otel-observability-architect (if monitoring gaps found), incident-learning-loop (after incident reveals gaps).
The on-call test
Imagine it's 3 AM. An alert fires. The on-call person has never seen this service. Can they:
- Understand what the alert means in 30 seconds?
- Find the relevant dashboard in 1 minute?
- Identify whether it's getting better or worse in 2 minutes?
- Take the first mitigation action in 5 minutes?
- Escalate to the right person if needed?
If any answer is "no," the system is not operable.
Runbook quality checklist
A good runbook:
- Starts with "when you see X, do Y" (not theory).
- Has concrete commands, not "check the database."
- Includes decision trees for ambiguous symptoms.
- Was tested by someone who didn't write it.
- Was updated after the last incident.
Red flags
- Alert fires, but no one knows the first action.
- Dashboard shows 20 graphs but doesn't answer "is it broken?"
- Recovery depends on one person's tribal knowledge.
- Ownership unclear at service boundaries.
- Runbook is a copy-paste from 2 years ago.
- "Safe mode" or degraded mode doesn't exist.
- On-call rotation includes people who've never touched the service.
Output format
- Operability assessment (operable / gaps / not ready)
- Ownership clarity (clear / ambiguous / missing)
- Runbook quality (actionable / stale / missing)
- Alert quality (actionable / noisy / missing)
- On-call experience (humane / painful / unsustainable)
- Top 3 improvements (highest impact on mean-time-to-recovery)
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.
- 8d ago First seen · 53 lines · 32 tokens per session scan A b6e092081971
operational-excellence-enforcer is a skill published in the GitHub repository caiaffa/claude-code-ultimate-engineering-system (17 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 505 once invoked, about $0.0002 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…