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.
npx skills add jamestorrevillas/dev-skills --skill incident-responsegit clone --depth 1 https://github.com/jamestorrevillas/dev-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/skills/jamestorrevillas/dev-skills/incident-response)<a href="https://agentmods.dev/skills/jamestorrevillas/dev-skills/incident-response"><img src="https://agentmods.dev/badge/skills/jamestorrevillas/dev-skills/incident-response/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/skills/jamestorrevillas/dev-skills/incident-response"><img src="https://agentmods.dev/badge/skills/jamestorrevillas/dev-skills/incident-response.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.00065 | $0.00824 |
| Opus 5 | $0.00032 | $0.00412 |
| Sonnet 5 | $0.00013 | $0.00165 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
incident-response 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 9d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Response
The Five Phases
DETECT → ASSESS → RESPOND → RESOLVE → LEARN
Every incident touches all five. Never skip LEARN — it's the only one that prevents recurrence.
Phase 1: Detect & Assess (First 5 Minutes)
1. What is broken? (specific service, feature, endpoint)
2. Who is affected? (all users, subset, specific region)
3. What is the impact? (data loss? revenue? user-facing?)
4. When did it start? (correlate with recent deploys/changes)
5. Severity: P1 (all users, data loss) / P2 (major feature) / P3 (minor)
Communicate immediately — even if you don't know the cause yet:
"We're investigating an issue with [service].
Impact: [who is affected].
We'll update in 15 minutes."
Phase 2: Respond (During Incident)
Incident Roles
- Incident Commander — coordinates, communicates, makes calls
- Technical Lead — investigates and fixes
- Communicator — updates stakeholders
Response Checklist
- Create incident channel/ticket
- Assign IC and Technical Lead
- Begin investigation (check logs, metrics, recent changes)
- Post status updates every 15-30 minutes
- Consider rollback if recent deploy is suspect
- Escalate if not resolved in [your SLA]
Rollback Decision Criteria
Roll back immediately if:
- Root cause is a recent deploy (< 24h)
- Fix is not immediately obvious
- User impact is severe
Phase 3: Resolve
Document as you go:
Timeline:
[time] - Incident detected: [symptom]
[time] - Identified probable cause: [cause]
[time] - Applied fix: [action taken]
[time] - Monitoring for stability
[time] - Incident resolved
Phase 4: Post-Mortem (Within 48h)
Post-Mortem Template
## Incident: [title]
**Date:** | **Duration:** | **Severity:**
### Summary
[2-3 sentences: what happened and impact]
### Timeline
[Chronological events from detection to resolution]
### Root Cause
[The actual cause — not the symptom]
### Contributing Factors
[Conditions that allowed this to happen]
### What Went Well
[Things that helped during response]
### Action Items
| Action | Owner | Due Date |
|--------|-------|----------|
| [preventive fix] | [name] | [date] |
| [monitoring improvement] | [name] | [date] |
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.
- 9d ago First seen · 134 lines · 0 tokens per session scan A 4597bd6ad168
incident-response is a skill published in the GitHub repository jamestorrevillas/dev-skills (3 stars, last pushed 5mo ago), licensed MIT. It adds 65 tokens to every session and 824 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-31.
Other skills, from other repositories
log-analyzer
Senior-SRE log analysis specialist. Use when investigating incidents from logs, triaging error spikes, extracting timelines, correlating distributed traces, or separating signal from noise across plain-text, JSON (slog/zap), syslog, journald, container, and Kubernetes logs. ALWAYS use when the user asks to "analyze…
incident-postmortem
Incident post-mortem specialist for writing blameless post-mortems, extracting timelines from logs/events, conducting root cause analysis (5-Why, fishbone), classifying severity, and generating tracked action items. ALWAYS use when writing a post-mortem, reviewing an incident, extracting a timeline, performing root…
systematic-debugging
Use when debugging, diagnosing, or investigating any bug, test failure, flaky test, race condition, unexpected behavior, build failure, production incident, third-party breakage, root cause analysis, or performance regression before proposing fixes.
hotfix
Fixes an observed defect with reproducible evidence in one call: writes a short trace doc before touching code, implements the fix, and backs it with a regression test written before the fix. Production incidents are the motivating case, not a gate. When blocked, it halts by name and saves the doc for a later call to…
sap-sac-scripting
Comprehensive SAC scripting skill for SAP Analytics Cloud Analytics Designer and Optimized Story Experience. This skill should be used when the user asks to "create SAC script", "debug Analytics Designer", "optimize SAC performance", "planning operations in SAC", "filter data in SAC", "use DataSource API", "chart…
sapui5-linter
Use this skill when working with the UI5 Linter (@ui5/linter) for static code analysis of SAPUI5/OpenUI5 applications and libraries. Covers setup, configuring linting rules, running the linter to detect deprecated APIs, global variable usage, CSP violations, and manifest issues. Supports autofix for deprecated API…