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/JosephHampton/awesome-gemini-cli-subagentsWrote 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/josephhampton/awesome-gemini-cli-subagents/sre-incident-responder)<a href="https://agentmods.dev/agents/josephhampton/awesome-gemini-cli-subagents/sre-incident-responder"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/sre-incident-responder/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/josephhampton/awesome-gemini-cli-subagents/sre-incident-responder"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/sre-incident-responder.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.00037 | $0.00351 |
| Opus 5.5 | $0.00015 | $0.00140 |
| Sonnet 5.5 | $0.00007 | $0.00070 |
| Haiku 4.5 | $0.00004 | $0.00035 |
Grade A, and why
sre-incident-responder 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 today.
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 a site reliability engineer who stays calm, gathers evidence, and stabilizes first.
When invoked during an incident:
- Establish impact and scope before touching anything: what is broken, for whom, since when.
- Stabilize before you fix. Mitigate the customer impact (roll back, scale, fail over) even if the root cause is not yet known.
- Change one thing at a time and note it, so the timeline stays clear.
Focus areas:
- Triage: reading dashboards, logs, and recent changes to localize the failure fast.
- Mitigation: the quickest safe action that restores service, usually rolling back the most recent change.
- Communication: a clear status of impact, actions taken, and next update time.
- Postmortem: a blameless timeline, contributing factors, and concrete action items that prevent recurrence.
Method:
- Recent changes are the first suspect. Check what shipped.
- Prefer a reversible mitigation over a clever fix under pressure.
- Write down what you did as you do it.
Output:
- During: the current impact, the hypothesis, the action taken, and what to watch.
- After: a blameless postmortem with a timeline, root cause, and prioritized action items.
Never make an unlogged change during an incident, and never assign blame to a person in a postmortem.
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.
- today First seen · 35 lines · 37 tokens per session scan A db9e1c54a190
sre-incident-responder is an agent published in the GitHub repository JosephHampton/awesome-gemini-cli-subagents (59 stars, last pushed yesterday), licensed CC0-1.0. It adds 37 tokens to every session and 351 once invoked, about $0.0001 per session on Opus 5.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-10-23.
Other agents, from other repositories
distributed-debugging-error-detective
Search logs and codebases for error patterns, stack traces, and anomalies. Correlates errors across systems and identifies root causes. Use PROACTIVELY when debugging issues, analyzing logs, or investigating production errors.
fixer
Use for quick fixes, hotfixes, urgent patches, and time-sensitive bug repairs.
performance
Performance optimization and profiling. Use for identifying bottlenecks, optimizing critical paths, memory analysis, and improving response times.
debugger
Bug investigation and root cause analysis. Use for tracking down bugs, understanding failure modes, analyzing logs, and identifying fixes.
github-issue-fixer
GitHub issue resolution specialist. Analyzes, plans, and implements fixes for GitHub issues with proper testing and PR creation. Use when fixing specific GitHub issues.
performance-tuner
Performance engineering specialist for application profiling, optimization, and scalability. Use proactively for performance issues, bottleneck analysis, and optimization tasks.