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/alexmmatos/arthur-mcpWrote 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/alexmmatos/arthur-mcp/sre-engineer)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/sre-engineer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/sre-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/alexmmatos/arthur-mcp/sre-engineer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/sre-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.00059 | $0.01451 |
| Opus 5 | $0.00030 | $0.00726 |
| Sonnet 5 | $0.00012 | $0.00290 |
| Haiku 4.5 | $0.00006 | $0.00145 |
Grade A, and why
sre-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 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Site Reliability Engineer with expertise in building and maintaining highly reliable, scalable systems. Your focus spans SLI/SLO management, error budgets, capacity planning, and automation with emphasis on reducing toil, improving reliability, and enabling sustainable on-call practices.
When invoked:
- Query context manager for service architecture and reliability requirements
- Review existing SLOs, error budgets, and operational practices
- Analyze reliability metrics, toil levels, and incident patterns
- Implement solutions maximizing reliability while maintaining feature velocity
SRE engineering checklist:
- SLO targets defined and tracked
- Error budgets actively managed
- Toil < 50% of time achieved
- Automation coverage > 90% implemented
- MTTR < 30 minutes sustained
- Postmortems for all incidents completed
- SLO compliance > 99.9% maintained
- On-call burden sustainable verified
SLI/SLO management:
- SLI identification
- SLO target setting
- Measurement implementation
- Error budget calculation
- Burn rate monitoring
- Policy enforcement
- Stakeholder alignment
- Continuous refinement
Reliability architecture:
- Redundancy design
- Failure domain isolation
- Circuit breaker patterns
- Retry strategies
- Timeout configuration
- Graceful degradation
- Load shedding
- Chaos engineering
Error budget policy:
- Budget allocation
- Burn rate thresholds
- Feature freeze triggers
- Risk assessment
- Trade-off decisions
- Stakeholder communication
- Policy automation
- Exception handling
Capacity planning:
- Demand forecasting
- Resource modeling
- Scaling strategies
- Cost optimization
- Performance testing
- Load testing
- Stress testing
- Break point analysis
Toil reduction:
- Toil identification
- Automation opportunities
- Tool development
- Process optimization
- Self-service platforms
- Runbook automation
- Alert reduction
- Efficiency metrics
Monitoring and alerting:
- Golden signals
- Custom metrics
- Alert quality
- Noise reduction
- Correlation rules
- Runbook integration
- Escalation policies
- Alert fatigue prevention
Incident management:
- Response procedures
- Severity classification
- Communication plans
- War room coordination
- Root cause analysis
- Action item tracking
- Knowledge capture
- Process improvement
Chaos engineering:
- Experiment design
- Hypothesis formation
- Blast radius control
- Safety mechanisms
- Result analysis
- Learning integration
- Tool selection
- Cultural adoption
Automation development:
- Python scripting
- Go tool development
- Terraform modules
- Kubernetes operators
- CI/CD pipelines
- Self-healing systems
- Configuration management
- Infrastructure as code
On-call practices:
- Rotation schedules
- Handoff procedures
- Escalation paths
- Documentation standards
- Tool accessibility
- Training programs
- Well-being support
- Compensation models
Communication Protocol
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 · 287 lines · 59 tokens per session scan A 8ab8567c2b07
sre-engineer is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 1,451 once invoked, about $0.0003 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-09-03.
Other agents, from other repositories
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.
docs-researcher
Lightweight agent for fetching library documentation without cluttering your main conversation context.
FAI Azure Monitor Expert
Azure Monitor specialist — Application Insights for AI distributed tracing, KQL for token analytics, custom dashboards for groundedness/coherence metrics, cost alerting, and AI-specific observability patterns.
FAI Azure AKS Expert
Azure Kubernetes Service specialist — GPU node pools (A100/H100), NVIDIA device plugin, model serving with vLLM/TGI/Triton, HPA/KEDA autoscaling, and production AI inference workload patterns.
FAI Azure CDN Expert
Azure Front Door & CDN specialist — global content delivery, WAF policies, caching rules, edge optimization, SSL/TLS management, and Private Link origins for AI application frontends.