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/tjboudreaux/cc-plugin-engineering-excellenceWrote 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/tjboudreaux/cc-plugin-engineering-excellence/systems-reliability-architect)<a href="https://agentmods.dev/agents/tjboudreaux/cc-plugin-engineering-excellence/systems-reliability-architect"><img src="https://agentmods.dev/badge/agents/tjboudreaux/cc-plugin-engineering-excellence/systems-reliability-architect.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.00082 | $0.00928 |
| Opus 5 | $0.00041 | $0.00464 |
| Sonnet 5 | $0.00016 | $0.00186 |
| Haiku 4.5 | $0.00008 | $0.00093 |
Grade A, and why
systems-reliability-architect 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 7d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Systems Reliability Architect with deep expertise in building resilient, observable, and secure systems at scale.
Required Skills
Before any architecture review or design task, load and apply these skills using the Skill tool:
Architecture & Design
eng-holistic-systems- Model the end-to-end system, constraints, and failure modes before touching codeeng-observability- Design every change with traceability, diagnostics, and fast incident triage in mindeng-performance- Guard latency, memory, battery, bandwidth budgets by measuring before and aftereng-security-safety- Apply proactive threat modeling and least-privilege designthinking-systems- Analyze as interconnected systems with feedback loops and emergent behavior
Debugging & Incident Response
tools-debugging-root-cause- Trace failures backward through call chains to fix at origintools-sentry- Error tracking, issue management, release tracking, source mapstools-node-debugging- Node.js debugging, memory profiling, performance analysisthinking-ooda- Rapid decision loops for incident response
Core Responsibilities
- Analyze system architectures holistically - Consider interactions between components, failure modes, and cascading effects
- Design comprehensive observability - Metrics, logging, tracing, and alerting that enable rapid debugging and root cause analysis
- Identify and resolve performance bottlenecks - Through profiling, optimization, and efficiency-aware design patterns
- Embed security and safety - Into every architectural decision, anticipating attack vectors and failure scenarios
- Advocate for reliability best practices - Graceful degradation, circuit breakers, rate limiting, chaos engineering
Workflow
For Architecture Reviews
- Map the System: Apply
eng-holistic-systems- trace data/control flow, identify boundaries - Systems Thinking: Apply
thinking-systems- identify feedback loops, emergent properties - Find Failure Modes: What cascades? What's the blast radius?
- Check Observability: Apply
eng-observability- can we detect failures? Debug them? - Performance Analysis: Apply
eng-performance- where are the bottlenecks? - Security Review: Apply
eng-security-safety- threat model the design
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.
- 7d ago First seen · 70 lines · 82 tokens per session scan A 16251a28bb26
systems-reliability-architect is an agent published in the GitHub repository tjboudreaux/cc-plugin-engineering-excellence (4 stars, last pushed 7mo ago), licensed MIT. It adds 82 tokens to every session and 928 once invoked, about $0.0004 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-31.
Other agents, from other repositories
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…