incident-response

incident-response is a skill for Claude Code, Codex from w95/awesome-claude-corporate-skills. It costs 51 tokens per session (328 once invoked), scanned A, original, MIT.

An incident-response guide for handling live production problems, from detection and severity assessment through recovery and a postmortem.

In plain words
What is it for?
It helps classify incidents, coordinate updates, reduce impact, verify fixes, and record follow-up work after resolution.
Why use it?
It gives the team a shared process during an outage, when fast decisions, clear communication, and assigned responsibility matter.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps classify incidents, coordinate updates, reduce impact, verify fixes, and record follow-up work after resolution.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/w95/awesome-claude-corporate-skills/incident-response
Install

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.

Any agent
npx skills add w95/awesome-claude-corporate-skills --skill incident-response
Clone the repo
git clone --depth 1 https://github.com/w95/awesome-claude-corporate-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for incident-response

README.md
[![agentmods](https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/incident-response/github.svg)](https://agentmods.dev/skills/w95/awesome-claude-corporate-skills/incident-response)
Your own site
<a href="https://agentmods.dev/skills/w95/awesome-claude-corporate-skills/incident-response"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-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.

agentmods 80×15 button for incident-response

Your own site · 80×15
<a href="https://agentmods.dev/skills/w95/awesome-claude-corporate-skills/incident-response"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/incident-response.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 328 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00051 $0.00328
Opus 5 $0.00026 $0.00164
Sonnet 5 $0.00010 $0.00066
Haiku 4.5 $0.00005 $0.00033

Measured 9d ago against content hash 798b5d9d5611, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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.

08-it-engineering/incident-response/SKILL.md · 34 lines

What it actually says

Incident Response

Guide incident response from detection through resolution and postmortem.

Severity Classification

Level Criteria Response Time
SEV1 Service down, all users affected Immediate, all-hands
SEV2 Major feature degraded, many users affected Within 15 min
SEV3 Minor feature issue, some users affected Within 1 hour
SEV4 Cosmetic or low-impact issue Next business day

Response Framework

  1. Triage: Classify severity, identify scope, assign incident commander
  2. Communicate: Status page, internal updates, customer comms if needed
  3. Mitigate: Stop the bleeding first, root cause later
  4. Resolve: Implement fix, verify, confirm resolution
  5. Postmortem: Blameless review, 5 whys, action items

Communication Templates

Provide clear, factual updates at regular cadence. Include: what's happening, who's affected, what we're doing, when the next update is.

Postmortem Format

Blameless. Focus on systems and processes. Include timeline, root cause analysis (5 whys), what went well, what went poorly, and action items with owners and due dates.

Changes

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.

  1. 9d ago First seen · 34 lines · 51 tokens per session scan A 798b5d9d5611

Subscribe to this mod's changes

incident-response is a skill published in the GitHub repository w95/awesome-claude-corporate-skills (198 stars, last pushed 6mo ago), licensed MIT. It adds 51 tokens to every session and 328 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-09-03.

Related

Other skills, from other repositories