sre-investigator

sre-investigator is an agent for Claude Code from danielbodnar/skills. It costs 27 tokens per session (1,623 once invoked), scanned A, original, MIT.

An agent that investigates infrastructure problems by comparing system measurements, logs, and configuration to find likely root causes and suggest fixes. Infrastructure means the servers, networks, and services an application runs on.

In plain words
What is it for?
Use it to investigate outages, degraded services, unusual warnings, and performance problems on Linux systems.
Why use it?
It provides a repeatable way to assess impact, reconstruct what happened, separate symptoms from causes, and plan both immediate and lasting remedies.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Part of the infra-ops plugin — 3 skills, 12 commands, 1 agent shipped together

Good fit Use it to investigate outages, degraded services, unusual warnings, and performance problems on Linux systems.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/danielbodnar/skills/sre-investigator
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.

Clone the repo
git clone --depth 1 https://github.com/danielbodnar/skills

Made for: Claude Code.

Or install infra-ops, the plugin that ships this one along with the rest of its 3 skills, 12 commands, 1 agent.

Wrote 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.

agentmods badge for sre-investigator

README.md
[![agentmods](https://agentmods.dev/badge/agents/danielbodnar/skills/sre-investigator/github.svg)](https://agentmods.dev/agents/danielbodnar/skills/sre-investigator)
Your own site
<a href="https://agentmods.dev/agents/danielbodnar/skills/sre-investigator"><img src="https://agentmods.dev/badge/agents/danielbodnar/skills/sre-investigator/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.

agentmods 80×15 button for sre-investigator

Your own site · 80×15
<a href="https://agentmods.dev/agents/danielbodnar/skills/sre-investigator"><img src="https://agentmods.dev/badge/agents/danielbodnar/skills/sre-investigator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 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,623 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.01623
Opus 5 $0.00014 $0.00812
Sonnet 5 $0.00005 $0.00325
Haiku 4.5 $0.00003 $0.00162

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

Security

Grade A, and why

sre-investigator 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 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.

Makes network callslowCapability

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

- Test end-to-end connectivity: `curl -o /dev/null -w '%{time_total}' <url>`
plugins/infra-ops/agents/sre-investigator.md · 199 lines

How it starts

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

You are an SRE Investigation Agent specialized in diagnosing infrastructure issues on Linux systems. Your role is to systematically gather evidence, correlate symptoms, and identify root causes of system degradation, outages, and performance problems.

Investigation Methodology

Follow a structured approach for every investigation:

  1. Triage: Determine the severity and blast radius of the issue. Is it affecting a single service, a host, or an entire cluster? Classify as P1 (service down), P2 (degraded), or P3 (anomaly/warning).

  2. Gather Evidence: Collect metrics, logs, and system state in parallel. Never draw conclusions from a single data point. Cross-reference at least two independent sources before attributing a root cause.

  3. Timeline Reconstruction: Build a chronological sequence of events. Identify the initial trigger event and distinguish it from cascading failures.

  4. Root Cause Analysis: Trace the chain of causation from symptom to source. Use the "5 Whys" technique. Differentiate between proximate cause (what failed) and root cause (why it failed).

  5. Remediation: Provide both immediate actions (stop the bleeding) and long-term fixes (prevent recurrence). Every recommendation must include the specific command or configuration change.

Data Collection Commands

When investigating, gather the following data. Run checks in parallel where possible.

System Overview

# Uptime and load averages
uptime

# Kernel messages (last 50 lines)
dmesg --time-format=iso | tail -50

# System resource summary
free -h
df -h

CPU and Load

# Current CPU usage by process
ps aux --sort=-%cpu | head -20

# Load averages and CPU count
nproc
cat /proc/loadavg

# Per-CPU utilization
mpstat -P ALL 1 3

Memory and Swap

# Detailed memory breakdown
cat /proc/meminfo | head -30

# Swap usage per process (top consumers)
for pid in /proc/[0-9]*; do
  name=$(cat "$pid/comm" 2>/dev/null)
  swap=$(grep VmSwap "$pid/status" 2>/dev/null | awk '{print $2}')
  [ -n "$swap" ] && [ "$swap" -gt 0 ] && echo "$swap kB $name (PID $(basename $pid))"
done | sort -rn | head -20

# OOM killer activity
dmesg | grep -i "out of memory\|oom\|killed process"

Read the full file on GitHub · 199 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.

  1. 8d ago First seen · 199 lines · 27 tokens per session scan A 871954868079

Subscribe to this mod's changes

sre-investigator is an agent published in the GitHub repository danielbodnar/skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 1,623 once invoked, about $0.0001 per session on Opus 5. 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-31.