sre

sre is an agent for Claude Code from me2resh/apexyard. It costs 41 tokens per session (413 once invoked), scanned A, original, MIT.

A site reliability engineering agent for keeping software systems dependable, observable, and able to recover from failures. Site reliability engineering applies software practices to running systems.

In plain words
What is it for?
Use it for incident response, reliability investigations, monitoring and alerting work, and on-call planning.
Why use it?
It helps teams respond to production incidents, service-level objective (SLO) breaches, and operational problems involving monitoring, alerts, or on-call work.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/me2resh/apexyard/sre
Clone the repo
git clone --depth 1 https://github.com/me2resh/apexyard

Made for: Claude Code.

Wrote 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.

agentmods badge for sre

README.md
[![agentmods](https://agentmods.dev/badge/agents/me2resh/apexyard/sre.svg)](https://agentmods.dev/agents/me2resh/apexyard/sre)
Your own site
<a href="https://agentmods.dev/agents/me2resh/apexyard/sre"><img src="https://agentmods.dev/badge/agents/me2resh/apexyard/sre.svg" alt="Measured on agentmods" height="20"></a>
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 413 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00041 $0.00413
Opus 5 $0.00020 $0.00206
Sonnet 5 $0.00008 $0.00083
Haiku 4.5 $0.00004 $0.00041

Measured 4d ago against content hash 9b384dea72f8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

sre 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 4d 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.

.claude/agents/sre.md · 24 lines

What it actually says

Saif — Site Reliability Engineer (SRE)

Read and adopt @roles/engineering/sre.md for full identity, responsibilities, CAN / CANNOT boundaries, and handoff rules. The role file is the canonical persona definition; this file is the thin runtime wrapper that owns model + tool-restriction + agent metadata only.

When reading a managed-project codebase (e.g. tracing an incident through service code), prefer mcp__apexyard-search__search_code (and search_docs for docs) over grep + Read — it's semantic, returns targeted excerpts, and costs ~3–5× fewer tokens. Fall back to grep/Read only when an MCP query returns nothing relevant (e.g. the project isn't indexed). This mirrors the main loop's standing rule; sub-agents must follow it too (apexyard#475).

Activation context

This agent activates per .claude/rules/role-triggers.md — auto-triggers on the conditions listed in that file's trigger table, plus prompted activation ("act as SRE"). The ## Activation mode section in the role file determines whether activation spawns this sub-agent (isolated-work-class) or adopts the persona in-thread (in-flow-class). See AgDR-0050 § Axis 6 for the design.


Part of ApexYard — multi-project SDLC framework for Claude Code · MIT.

Changes

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.

  1. 4d ago First seen · 24 lines · 41 tokens per session scan A 9b384dea72f8

Subscribe to this mod's changes

sre is an agent published in the GitHub repository me2resh/apexyard (498 stars, last pushed 3d ago), licensed MIT. It adds 41 tokens to every session and 413 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.