devops-sre

An infrastructure troubleshooting agent that follows four stages: respond first, investigate the cause, fix the issue, and evaluate the result. Infrastructure means the servers, networks, and services that applications depend on.

In plain words
What is it for?
Use it when diagnosing service outages, deployment problems, or other operational issues involving application infrastructure.
Why use it?
It gives incident work a clear order, helping teams move from an active problem to a tested resolution without skipping investigation or follow-up.

Agent

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/florianbruniaux/claude-code-ultimate-guide/devops-sre
Clone the repo
git clone --depth 1 https://github.com/FlorianBruniaux/claude-code-ultimate-guide
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,101 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. Scan, not verified.
Origin unknown 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.

ModelPer sessionOnce invoked
Fable 5 $0.00024 $0.01101
Opus 5 $0.00012 $0.00550
Sonnet 5 $0.00005 $0.00220
Haiku 4.5 $0.00002 $0.00110

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

Security

Grade C, and why

devops-sre scanned grade C with 2 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

- `rm -rf` outside tmp

Makes network callslowCapability

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

- [ ] Test connectivity: `kubectl exec -it <pod> -- curl <svc>:<port>`
examples/agents/devops-sre.md · 171 lines

The source is not reproduced here

Licensed CC-BY-SA-4.0

The repository is licensed CC-BY-SA-4.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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.

  1. 3d ago First seen · 171 lines · 24 tokens per session scan C e03ddd929431

Subscribe to this mod's changes

devops-sre is an agent published in the GitHub repository FlorianBruniaux/claude-code-ultimate-guide (5,863 stars, last pushed yesterday), licensed CC-BY-SA-4.0. It adds 24 tokens to every session and 1,101 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other agents, from other repositories

system-architect

Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…

rtk-ai/rtk · 0 tokens

lane-critic

Lane plan-critique compressor. Coverage auditor only — owns/verify gaps. No product edits. Use for stages.plancritique when provider is opencode.

VKirill/claude-lane-stack · 33 tokens

run-supervisor

Daytime run supervisor. Starts and visibly watches one durable deterministic run controller until every writer lane is accepted or the run is blocked. Use proactively for multi-lane work, параллельные задачи, запусти и следи, доведи run до конца.

VKirill/claude-lane-stack · 57 tokens

code-reviewer

Use when a major project step completes and needs review against the original plan and coding standards. Examples: Context: User finished implementing user authentication as step 3 of plan. user: "I've finished implementing the user authentication system as outlined in step 3 of our plan" assistant: "Let me use the…

axiomantic/spellbook · 190 tokens

adapter_cursor

Cursor runs as agent or its cursor-agent alias; cursor names the IDE and is intentionally outside binary discovery. RimZ installs additive user hooks in /.cursor/hooks.json and a canonical command statusline in /.cursor/cli-config.json, launches a verified resolved path or the provider-unique cursor-agent alias, and…

rimio-ai/rimz · 0 tokens

AGENTS

Local contract for crates/rimz/src/agents/ — the integration layer. Extends crates/rimz/AGENTS.md.

rimio-ai/rimz · 0 tokens