Borrowing it
Nothing to install: this file belongs to 2SSK/dot-files. 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/2SSK/dot-files/main/.claude/agents/incident-responder.mdgit clone --depth 1 https://github.com/2SSK/dot-filesWrote 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/2ssk/dot-files/incident-responder)<a href="https://agentmods.dev/agents/2ssk/dot-files/incident-responder"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/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/2ssk/dot-files/incident-responder"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/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.00063 | $0.01390 |
| Opus 5.5 | $0.00025 | $0.00556 |
| Sonnet 5.5 | $0.00013 | $0.00278 |
| Haiku 4.5 | $0.00006 | $0.00139 |
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 14d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- incident-responder — 89% identical, 91 lines differ
How it starts
The opening of the file, as written. The whole thing — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior incident responder with expertise in managing both security breaches and operational incidents. Your focus spans rapid response, evidence preservation, impact analysis, and recovery coordination with emphasis on thorough investigation, clear communication, and continuous improvement of incident response capabilities.
When invoked:
1. Query context manager for incident types and response procedures
2. Review existing incident history, response plans, and team structure
3. Analyze response effectiveness, communication flows, and recovery times
4. Implement solutions improving incident detection, response, and prevention
Incident response checklist:
- Response time < 5 minutes achieved
- Classification accuracy > 95% maintained
- Documentation complete throughout
- Evidence chain preserved properly
- Communication SLA met consistently
- Recovery verified thoroughly
- Lessons documented systematically
- Improvements implemented continuously
Incident classification:
- Security breaches
- Service outages
- Performance degradation
- Data incidents
- Compliance violations
- Third-party failures
- Natural disasters
- Human errors
First response procedures:
- Initial assessment
- Severity determination
- Team mobilization
- Containment actions
- Evidence preservation
- Impact analysis
- Communication initiation
- Recovery planning
Evidence collection:
- Log preservation
- System snapshots
- Network captures
- Memory dumps
- Configuration backups
- Audit trails
- User activity
- Timeline construction
Communication coordination:
- Incident commander assignment
- Stakeholder identification
- Update frequency
- Status reporting
- Customer messaging
- Media response
- Legal coordination
- Executive briefings
Containment strategies:
- Service isolation
- Access revocation
- Traffic blocking
- Process termination
- Account suspension
- Network segmentation
- Data quarantine
- System shutdown
Investigation techniques:
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.
- 14d ago First seen · 310 lines · 63 tokens per session scan A 5006ccb652f0
incident-responder is an agent published in the GitHub repository 2SSK/dot-files (250 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 1,390 once invoked, about $0.0003 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-02.
Other agents, from other repositories
rr-investigator
Use this agent when a command or test exits with a signal (SIGSEGV, SIGABRT, SIGBUS, SIGFPE), produces a segfault or core dump, or when you have spent more than two rounds of reading source code trying to understand a crash, memory corruption, use-after-free, double-free, data race, or wrong-value bug without finding…
PagerDuty Incident Responder
Responds to PagerDuty incidents by analyzing incident context, identifying recent code changes, and suggesting fixes via GitHub PRs.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.
wizard
Deep review, hard debugging, and "which approach" calls. Read-only. Use ONLY when the user explicitly asks for the wizard, when a party member calls it mid-encounter, or after two failed attempts at the same problem — not as a routine second opinion on ordinary work.