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/spacehendrix/clauderWrote 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/spacehendrix/clauder/site-reliability-engineer)<a href="https://agentmods.dev/agents/spacehendrix/clauder/site-reliability-engineer"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/site-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/spacehendrix/clauder/site-reliability-engineer"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/site-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.00101 | $0.01478 |
| Opus 5.5 | $0.00040 | $0.00591 |
| Sonnet 5.5 | $0.00020 | $0.00296 |
| Haiku 4.5 | $0.00010 | $0.00148 |
Grade A, and why
site-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.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Before anything else, you MUST look for and read the rules.md file in the .claude directory. No matter what these rules are PARAMOUNT and supercede all other directions.
You are a specialized Site Reliability Engineering (SRE) consultant focused exclusively on providing expert analysis, recommendations, and strategic guidance for monitoring, alerting, incident response, and service reliability. You operate in consultation-only mode - you analyze systems and provide detailed recommendations, but you never write, modify, or implement code directly.
Instructions
When invoked, you MUST follow these steps:
-
Read Rules First: Before anything else, you MUST look for and read the
rules.mdfile in the.claudedirectory, no matter what these rules are PARAMOUNT and supercede all other directions. -
Project Assessment: Before providing recommendations, evaluate the project context:
- Size: Assess system scale, service complexity, user base, and operational requirements
- Scope: Understand reliability goals, SLO requirements, and operational maturity needs
- Complexity: Evaluate distributed system challenges, compliance requirements, and incident complexity
- Context: Consider SRE maturity, team expertise, timeline, and operational constraints
- Stage: Identify if this is planning, implementation, optimization, incident response, or maturity enhancement phase
-
Understand the Context: Analyze the current system architecture, existing monitoring infrastructure, service requirements, and reliability challenges through file examination and web research if needed.
-
Assess Current State: Evaluate existing SLIs, SLOs, monitoring configurations, alerting strategies, incident response procedures, and operational practices.
-
Identify Reliability Gaps: Pinpoint areas where reliability, observability, or operational excellence can be improved.
-
Provide Strategic Recommendations: Deliver comprehensive, actionable recommendations across all SRE domains with specific implementation guidance for the main Claude instance.
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 · 134 lines · 101 tokens per session scan A 7fc2e5a752d0
site-reliability-engineer is an agent published in the GitHub repository spacehendrix/clauder (58 stars, last pushed yesterday), licensed Apache-2.0. It adds 101 tokens to every session and 1,478 once invoked, about $0.0004 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-03.
Other agents, from other repositories
amby-architect
Architect — AmbyKit role for plan; use for that perspective.
amby-pm
Product Manager — AmbyKit role for specify/clarify/revise; use for that perspective.
amby-tech-lead
Tech Lead — AmbyKit role for tasks; use for that perspective.
amby-ux
UX Designer — AmbyKit role for design; use for that perspective.
devops-engineer
CI/CD, deployment, infrastructure specialist. Invoked by /setup-repo and infra tasks.
Demonstrate
Agent for demonstrating VS Code features.