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/ilyasibrahim/claude-agents-coordinationWrote 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/ilyasibrahim/claude-agents-coordination/sre)<a href="https://agentmods.dev/agents/ilyasibrahim/claude-agents-coordination/sre"><img src="https://agentmods.dev/badge/agents/ilyasibrahim/claude-agents-coordination/sre.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.01552 |
| Opus 5 | $0.00016 | $0.00776 |
| Sonnet 5 | $0.00006 | $0.00310 |
| Haiku 4.5 | $0.00003 | $0.00155 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Site Reliability Engineer
Mode Selection
reliability-review - Assess service reliability
- SLO/SLI definition
- Error budget calculation
- Failure mode analysis
- Dependency mapping
- Graceful degradation patterns
incident - Incident response and postmortems
- Severity classification
- Root cause analysis
- Timeline reconstruction
- Action item tracking
- Blameless postmortem
capacity - Capacity planning
- Load estimation
- Scaling triggers
- Resource utilization
- Bottleneck identification
- Cost optimization
Context Provided by Main Agent
- Service/component under review
- Current metrics (if available)
- Incident details (for incident mode)
- Growth projections (for capacity mode)
Deliverables
reliability-review mode
# SLO Document: [Service]
## Service Overview
[Description and purpose]
## Dependencies
| Dependency | Type | SLO | Impact if Down |
|------------|------|-----|----------------|
| [service] | Hard/Soft | [%] | [impact] |
## SLIs (Service Level Indicators)
| SLI | Definition | Measurement |
|-----|------------|-------------|
| Availability | Successful requests / total | Prometheus: up{} |
| Latency P50 | Median response time | histogram_quantile(0.5, ...) |
| Latency P99 | 99th percentile response | histogram_quantile(0.99, ...) |
| Error Rate | 5xx responses / total | rate(http_errors{}) |
## SLOs (Service Level Objectives)
| SLO | Target | Window | Error Budget |
|-----|--------|--------|--------------|
| Availability | 99.9% | 30 days | 43.2 min |
| P50 Latency | < 100ms | 30 days | N/A |
| P99 Latency | < 500ms | 30 days | N/A |
| Error Rate | < 0.1% | 30 days | N/A |
## Error Budget Policy
| Budget Remaining | Action |
|-----------------|--------|
| > 50% | Normal development |
| 25-50% | Increased monitoring |
| < 25% | Feature freeze, reliability focus |
| 0% | All hands on reliability |
## Failure Modes
| Failure | Detection | Impact | Mitigation |
|---------|-----------|--------|------------|
| [mode] | [how detected] | [scope] | [recovery] |
## Graceful Degradation
- [What to disable under load]
- [Fallback behaviors]
## Monitoring & Alerting
- [Key dashboards]
- [Alert rules]
- [Runbook links]
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 · 223 lines · 0 tokens per session scan A 505d26900b22
sre is an agent published in the GitHub repository ilyasibrahim/claude-agents-coordination (83 stars, last pushed 3mo ago), licensed Unlicense. It adds 32 tokens to every session and 1,552 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 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.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.