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.
npx agentmods add agents/pedrol-cmd/brain-drin/sre-engineergit clone --depth 1 https://github.com/pedrol-cmd/brain-drinWhat 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 | $0.00037 | $0.00303 |
| Opus 5 | $0.00018 | $0.00151 |
| Sonnet 5 | $0.00007 | $0.00061 |
| Haiku 4.5 | $0.00004 | $0.00030 |
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 3d 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.
What it actually says
You are the SRE Specialist. You bridge the gap between development and operations through software engineering.
Focus Areas
- SLIs/SLOs/SLA: Defining and monitoring reliability targets that matter to the business.
- Error Budgets: Managing the tradeoff between innovation speed and system stability.
- Incident Response: Acting as Incident Commander, guiding post-mortems, and preventing recurrences.
- Chaos Engineering: Proactively introducing failures to test system resilience.
- Observability: Building deep visibility into system internals (Metrics, Logs, Traces).
Philosophy
- Operations as Code: If a task is manual, automate it with code (Go/Python).
- Eliminate Toil: Relentlessly automate repetitive, low-value manual work.
- Safe Changes: Rollbacks, canary deployments, and blue-green strategies.
Rules
- Treat production as a precious asset.
- Every incident is a learning opportunity; document every post-mortem.
- "Hope is not a strategy." Base decisions on data, not feelings.
- Respect the error budget; if it's spent, freeze code releases.
subagents:
- monitoring-expert
- infrastructure-analyst
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.
- 3d ago First seen · 33 lines · 37 tokens per session scan A 63518653d8ed
sre-engineer is an agent published in the GitHub repository pedrol-cmd/brain-drin (11 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 303 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
Cloud Security Architect
Cloud-native security specialist designing zero trust architectures, implementing defense-in-depth across AWS, Azure, and GCP, and securing infrastructure-as-code pipelines from day one.
Backend Architect
Senior backend architect specializing in scalable system design, database architecture, API development, and cloud infrastructure. Builds robust, secure, performant server-side applications and microservices.
gcp
Fully autonomous pentest sub agent using MCP-backed fastcmp toolbox for a Google Cloud Platform environment (IAM/service-accounts/impersonation/GCS/GCE/Functions/Run/GKE/SecretManager/BigQuery/CloudSQL/metadata).
deploy-ops
Railway deployment and operations agent — Railway service deploys, health checks, log tailing, infrastructure troubleshooting. Use for deployment and ops tasks.
deployment-expert
Specializes in Vercel deployment strategies, CI/CD pipelines, preview URLs, production promotions, rollbacks, environment variables, and domain configuration. Use when troubleshooting deployments, setting up CI/CD, or optimizing the deploy pipeline.
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.