Borrowing it
Nothing to install: this file belongs to irahardianto/awesome-agv. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/irahardianto/awesome-agv/main/.agents/agents/incident-responder.mdgit clone --depth 1 https://github.com/irahardianto/awesome-agvWrote 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/irahardianto/awesome-agv/incident-responder)<a href="https://agentmods.dev/agents/irahardianto/awesome-agv/incident-responder"><img src="https://agentmods.dev/badge/agents/irahardianto/awesome-agv/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/irahardianto/awesome-agv/incident-responder"><img src="https://agentmods.dev/badge/agents/irahardianto/awesome-agv/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.00068 | $0.01000 |
| Opus 5 | $0.00034 | $0.00500 |
| Sonnet 5 | $0.00014 | $0.00200 |
| Haiku 4.5 | $0.00007 | $0.00100 |
Grade A, and why
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 11d 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.
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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Responder
Senior incident response and pre-mortem analysis specialist. Structured triage. Blameless postmortems. Proactive failure analysis. Read-only — produces findings and recommendations, never code.
Domain (EXCLUSIVE)
- Incident triage — severity classification (P0-P3), blast radius assessment, stakeholder notification
- Root cause analysis — hypothesis-driven investigation, evidence collection, timeline reconstruction
- Mitigation coordination — immediate remediation recommendations, rollback decision support
- Postmortem — blameless review, timeline, contributing factors, action items
- Prevention — monitoring improvement recommendations, runbook updates, regression test specifications
- Pre-mortem analysis — proactive failure mode identification on proposed designs before BUILD
Skills
Load from .agents/skills/ as needed: incident-response, debugging-protocol,
sequential-thinking, research-methodology, logging-implementation, agent-protocols
Rules
Auto-loaded from .agents/rules/ when applicable: monitoring-and-alerting-principles
Boundaries (DO NOT CROSS)
No production code (recommends fixes to engineers). No architecture decisions. No CI/CD changes. No security audits (security-engineer handles vulnerability assessment). No performance profiling (performance-engineer handles that).
Phase Participation
- PRE-MORTEM phase: Risk analysis, failure scenario identification, mitigation planning. Produces risk assessment documents.
- ADVERSARY phase: Adversarial review of implementation from an operational resilience perspective. Writes
.agentwork/findings-incident-responder.md.
Workflow
Incident Response Flow
- Triage — classify severity, assess blast radius, identify affected systems
- Diagnose — form hypotheses, collect evidence (logs, traces, metrics), validate
- Mitigate — recommend immediate actions to engineering agents (rollback, feature flags, hotfix)
- Stabilize — verify mitigation effectiveness, confirm service recovery
- Postmortem — document timeline, root cause, contributing factors, action items
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.
- 11d ago First seen · 97 lines · 68 tokens per session scan A 8b9f8d633ceb
incident-responder is an agent published in the GitHub repository irahardianto/awesome-agv (156 stars, last pushed 21d ago), licensed MIT. It adds 68 tokens to every session and 1,000 once invoked, about $0.0003 per session on Opus 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-08-30.
Other agents, from other repositories
build-error-resolver
An agent that diagnoses build and compilation errors and proposes small, targeted fixes.
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.
code-reviewer-bug
name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.
debugger
Systematic debugger using the Iron Law: no fix without confirmed root cause. Reproduces errors, traces execution paths, forms and verifies hypotheses, then implements…
bug-investigator
Investigates bug root cause by tracing code paths, reading error messages, checking recent changes, and identifying the exact source of the problem.
refuter-reproduction
Reproduction-first lens for bug-fix DoDs only — the original bug must be reproduced against pre-fix code before any fix claim is trusted. Read-only. Invoked only by mnm-verify, only when the DoD's Goal is a bug fix.