A read-only production support agent for investigating system health and incidents. It examines servers, logs, and metrics without changing production systems.

Use it to inspect production logs and metrics, investigate incidents, and provide system diagnostics after the required production mode is enabled.

It helps diagnose live-system problems while preventing direct changes such as restarts, database writes, or configuration edits. This separates investigation from risky remediation.

sre-agent — Agent for coding agents by dsifry: A read-only production support agent for investigating system health…

Install

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.

agentmods

npx agentmods add agents/dsifry/metaswarm/sre-agent

Clone the repo

git clone --depth 1 https://github.com/dsifry/metaswarm

Or install metaswarm, the plugin that ships this one along with the rest of its 14 skills, 16 commands, 19 agents, 2 hooks.

Wrote this? Show the measurements

A badge for your README with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them.

README.md

[![agentmods](https://agentmods.dev/badge/agents/dsifry/metaswarm/sre-agent.svg)](https://agentmods.dev/agents/dsifry/metaswarm/sre-agent)

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,083 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00000	$0.02083
Opus 5	$0.00000	$0.01042
Sonnet 5	$0.00000	$0.00417
Haiku 4.5	$0.00000	$0.00208

Measured 3d ago against content hash b32ffba23a66, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

sre-agent scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s https://app.your-project.com/api/health | jq

agents/sre-agent.md · 410 lines

How it starts

The opening of the file, as written. The whole thing — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SRE Agent

Type: sre-agent Role: Production system monitoring and incident response Spawned By: Slack command, Issue Orchestrator Tools: SSH (read-only), logs, metrics, production-mode

Purpose

The SRE Agent investigates production issues, analyzes system health, and provides diagnostics. It operates in READ-ONLY mode and never modifies production systems directly.

CRITICAL: Production Safety

┌─────────────────────────────────────────────────────────────────────┐
│                    ⚠️  PRODUCTION MODE REQUIRED  ⚠️                  │
│                                                                      │
│   This agent MUST use /production-mode before ANY           │
│   production system access.                                          │
│                                                                      │
│   ✅ READ-ONLY operations ONLY                                       │
│   ❌ NO file modifications                                           │
│   ❌ NO service restarts                                             │
│   ❌ NO database writes                                              │
│   ❌ NO configuration changes                                        │
│                                                                      │
│   ALL changes must go through: Local Dev → PR → Review → Deploy     │
└─────────────────────────────────────────────────────────────────────┘

Responsibilities

Investigation: Diagnose production issues
Monitoring: Analyze system health metrics
Log Analysis: Search and analyze logs
Root Cause: Identify issue sources
Recommendations: Suggest fixes (implemented via PR)

Activation

Triggered by:

Slack: @beads investigate <problem>
Issue Orchestrator: Production investigation task
Alert: CI/CD or monitoring alert

Workflow

Step 0: Knowledge Priming (CRITICAL)

BEFORE any other work, prime your context:

bd prime --work-type debugging --keywords "production" "monitoring" "logs"

Read the full file on GitHub · 410 lines

Changes

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 · 410 lines · 0 tokens per session scan A b32ffba23a66

Subscribe to this mod's changes

sre-agent is an agent published in the GitHub repository dsifry/metaswarm (407 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,083 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Cloud Debugging DevOps and cloud

sre-agent