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/danielbodnar/skillsWrote 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/danielbodnar/skills/sre-investigator)<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.
<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>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.00027 | $0.01623 |
| Opus 5 | $0.00014 | $0.00812 |
| Sonnet 5 | $0.00005 | $0.00325 |
| Haiku 4.5 | $0.00003 | $0.00162 |
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>` 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:
-
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).
-
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.
-
Timeline Reconstruction: Build a chronological sequence of events. Identify the initial trigger event and distinguish it from cascading failures.
-
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).
-
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"
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 · 199 lines · 27 tokens per session scan A 871954868079
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.
Other agents, from other repositories
AWS Incident Triage
On-call SRE agent that drives structured CloudWatch-based incident investigation from alarms through root-cause hypothesis.
Cloud and SaaS Outage Triage
Distinguish upstream cloud or SaaS incidents from application failures before changing code, using live official-feed status and incident timelines.
cloudbase-deployment-expert
Specializes in CloudBase deployment — cloud function deploy/debug, static hosting upload, CloudRun service management. Use when troubleshooting deployments, checking build logs, or diagnosing runtime errors.
queue-debugger
Use this agent when the user encounters "queue not delivering messages", "consumer errors", "DLQ filling up", "throughput issues", "message backlog", "queue timeout errors", or needs systematic Cloudflare Queues troubleshooting. Examples.
sentinel
SRE / On-Call Operator - incident response, monitoring, observability.
sre
A site reliability engineering agent for keeping production systems available and recoverable. Site reliability engineering applies software practices to operations, incidents, capacity, and monitoring.