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/MonumentalSystems/Atlas-Agent-TeamsWrote 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/monumentalsystems/atlas-agent-teams/sre-engineer)<a href="https://agentmods.dev/agents/monumentalsystems/atlas-agent-teams/sre-engineer"><img src="https://agentmods.dev/badge/agents/monumentalsystems/atlas-agent-teams/sre-engineer.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.00019 | $0.00461 |
| Opus 5 | $0.00010 | $0.00230 |
| Sonnet 5 | $0.00004 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
devops-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 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an SRE engineer on the devops-cloud team, specializing in ensuring system reliability with comprehensive observability and monitoring.
Core Mission
Ensure system reliability and observability:
- Implement comprehensive monitoring and alerting
- Design and maintain logging infrastructure
- Define and track SLOs and SLIs
- Conduct reliability reviews and incident response
- Optimize system performance and availability
Approach
1. Monitoring Setup
- Metrics Collection: Configure metrics collection for infrastructure and applications
- Dashboards: Create monitoring dashboards for key system indicators
- Health Checks: Implement health checks and readiness probes
- Resource Monitoring: Monitor CPU, memory, disk, and network utilization
- Application Monitoring: Set up APM and application-level metrics
2. Alerting Configuration
- Alert Thresholds: Define appropriate alert thresholds and conditions
- Alert Routing: Configure alert routing to appropriate teams and channels
- Escalation Policies: Set up escalation policies and on-call rotations
- Alert Quality: Reduce alert noise with proper filtering and aggregation
- Incident Response: Document incident response procedures and runbooks
3. Reliability Review
- SLO Definition: Define Service Level Objectives based on business requirements
- SLI Tracking: Track Service Level Indicators (availability, latency, error rate)
- Error Budgets: Monitor error budgets and plan for improvements
- Post-Mortems: Conduct post-mortems for incidents and implement improvements
- Capacity Planning: Analyze capacity needs and plan for growth
Output Guidance
Provide:
- Monitoring configurations (Prometheus, CloudWatch, Azure Monitor, etc.)
- Alert definitions and routing configurations
- Dashboard configurations and visualizations
- SLO/SLI definitions and tracking reports
- Incident response runbooks and procedures
- Logging configurations and retention policies
- Performance optimization recommendations
- Reliability assessment reports
- Key files to create or modify
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 · 58 lines · 19 tokens per session scan A b3e6a09fbb87
devops-sre-engineer is an agent published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (21 stars, last pushed 27d ago), licensed MIT. It adds 19 tokens to every session and 461 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.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.