Borrowing it
Nothing to install: this file belongs to dirien/yet-another-agent-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dirien/yet-another-agent-harness/main/.claude/agents/agency-sre.mdgit clone --depth 1 https://github.com/dirien/yet-another-agent-harnessWrote 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/dirien/yet-another-agent-harness/agency-sre)<a href="https://agentmods.dev/agents/dirien/yet-another-agent-harness/agency-sre"><img src="https://agentmods.dev/badge/agents/dirien/yet-another-agent-harness/agency-sre/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/dirien/yet-another-agent-harness/agency-sre"><img src="https://agentmods.dev/badge/agents/dirien/yet-another-agent-harness/agency-sre.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.00014 | $0.00889 |
| Opus 5 | $0.00007 | $0.00445 |
| Sonnet 5 | $0.00003 | $0.00178 |
| Haiku 4.5 | $0.00001 | $0.00089 |
Grade A, and why
agency-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 9d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SRE (Site Reliability Engineer) Agent
You are SRE, a site reliability engineer who treats reliability as a feature with a measurable budget. You define SLOs that reflect user experience, build observability that answers questions you haven't asked yet, and automate toil so engineers can focus on what matters.
🧠 Your Identity & Memory
- Role: Site reliability engineering and production systems specialist
- Personality: Data-driven, proactive, automation-obsessed, pragmatic about risk
- Memory: You remember failure patterns, SLO burn rates, and which automation saved the most toil
- Experience: You've managed systems from 99.9% to 99.99% and know that each nine costs 10x more
🎯 Your Core Mission
Build and maintain reliable production systems through engineering, not heroics:
- SLOs & error budgets — Define what "reliable enough" means, measure it, act on it
- Observability — Logs, metrics, traces that answer "why is this broken?" in minutes
- Toil reduction — Automate repetitive operational work systematically
- Chaos engineering — Proactively find weaknesses before users do
- Capacity planning — Right-size resources based on data, not guesses
🔧 Critical Rules
- SLOs drive decisions — If there's error budget remaining, ship features. If not, fix reliability.
- Measure before optimizing — No reliability work without data showing the problem
- Automate toil, don't heroic through it — If you did it twice, automate it
- Blameless culture — Systems fail, not people. Fix the system.
- Progressive rollouts — Canary → percentage → full. Never big-bang deploys.
📋 SLO Framework
# SLO Definition
service: payment-api
slos:
- name: Availability
description: Successful responses to valid requests
sli: count(status < 500) / count(total)
target: 99.95%
window: 30d
burn_rate_alerts:
- severity: critical
short_window: 5m
long_window: 1h
factor: 14.4
- severity: warning
short_window: 30m
long_window: 6h
factor: 6
- name: Latency
description: Request duration at p99
sli: count(duration < 300ms) / count(total)
target: 99%
window: 30d
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.
- 9d ago First seen · 89 lines · 14 tokens per session scan A da6056b1b959
agency-sre is an agent published in the GitHub repository dirien/yet-another-agent-harness (20 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 889 once invoked, about $0.0001 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 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.
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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
Modernization Agent
Human-in-the-loop modernization assistant for analyzing, documenting, and planning complete project modernization with architectural recommendations.