incident-response

incident-response is a skill for Claude Code, Codex from medy-gribkov/arcana. It costs 37 tokens per session (2,452 once invoked), scanned A, original, Apache-2.0.

Engineering incident-response guidance for handling serious production problems, such as outages, data loss, security breaches, or degraded service. It covers severity levels, on-call runbooks, rollbacks, status updates, postmortems, and service-level objective breaches.

In plain words
What is it for?
Use it to classify incidents, assign response roles, follow recovery steps, roll back changes, update status pages, handle service-level target breaches, and write postmortems.
Why use it?
It gives teams a shared way to judge user impact, coordinate during an incident, communicate clearly, and restore service. It also helps them learn from failures without blaming individuals.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: positional $N argument.

Good fit Use it to classify incidents, assign response roles, follow recovery steps, roll back changes, update status pages, handle service-level target breaches, and write postmortems.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/medy-gribkov/arcana/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 medy-gribkov/arcana --skill incident-response
Clone the repo
git clone --depth 1 https://github.com/medy-gribkov/arcana

Made for: Claude Code, Codex.

Its marketplace also offers this one on its own, as the plugin incident-response/plugin install incident-response after adding the marketplace above.

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/medy-gribkov/arcana/incident-response/github.svg)](https://agentmods.dev/skills/medy-gribkov/arcana/incident-response)
Your own site
<a href="https://agentmods.dev/skills/medy-gribkov/arcana/incident-response"><img src="https://agentmods.dev/badge/skills/medy-gribkov/arcana/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/medy-gribkov/arcana/incident-response"><img src="https://agentmods.dev/badge/skills/medy-gribkov/arcana/incident-response.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,452 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00037 $0.02452
Opus 5 $0.00018 $0.01226
Sonnet 5 $0.00007 $0.00490
Haiku 4.5 $0.00004 $0.00245

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

Security

Grade A, and why

incident-response scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

kubectl exec -it deploy/api -- curl localhost:8080/debug/db
skills/incident-response/SKILL.md · 253 lines

How it starts

The opening of the file, as written. The whole thing — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Purpose

Handle production incidents with speed, clarity, and accountability. This skill provides frameworks for on-call response, structured communication, rollback execution, and learning from failures.

Severity Classification

  • SEV-1 (Critical): Complete service outage, data loss, or security breach. All hands on deck. Resolve in minutes.
  • SEV-2 (Major): Significant degradation affecting most users. Dedicated incident commander. Target resolution under 1 hour.
  • SEV-3 (Minor): Partial degradation, workaround available. On-call engineer handles. Target resolution under 4 hours.
  • SEV-4 (Low): Cosmetic issues, minor bugs, non-user-facing failures. Handle during business hours.
  • Classify based on user impact, not technical complexity. A simple bug affecting all users is higher severity than a complex bug affecting one.
  • Escalate severity upward when impact grows. Never downgrade severity during an active incident.

On-Call Runbooks

BAD - Vague runbook:

## Database Issues
If the database is slow, check the connections and maybe restart it.
Contact the DBA if it doesn't work.

GOOD - Actionable runbook with copy-paste commands:

## Runbook: Database Connection Pool Exhausted

### Symptoms
- API returns 503 errors
- Grafana alert: `db_active_connections > 95% of pool_size`
- Logs: "connection pool exhausted, 0 idle connections"

### Diagnose (< 1 minute)
    kubectl exec -it deploy/api -- curl localhost:8080/debug/db
    # Shows: active=100, idle=0, max=100, waiting=47

    psql -h $DB_HOST -c "SELECT count(*) FROM pg_stat_activity WHERE state='active';"

### Fix (choose one)
1. **Kill idle transactions** (safest):
       psql -h $DB_HOST -c "SELECT pg_terminate_backend(pid) FROM pg_stat_activity WHERE state='idle in transaction' AND query_start < now() - interval '5 min';"

2. **Increase pool size** (temporary):
       kubectl set env deploy/api DB_POOL_SIZE=200
       kubectl rollout restart deploy/api

3. **Rollback last deploy** (if caused by new code):
       kubectl rollout undo deploy/api

### Do NOT
- Do NOT restart the database. Active transactions will be lost.
- Do NOT increase pool size above 200 without DBA approval.

### Escalation
- Slack: #team-platform | PagerDuty: Platform On-Call

Read the full file on GitHub · 253 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 11d ago First seen · 253 lines · 37 tokens per session scan A ad8f6af1f2bf

Subscribe to this mod's changes

incident-response is a skill published in the GitHub repository medy-gribkov/arcana (1 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 2,452 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.