incident-commander

incident-commander is a skill for Claude Code, Codex from seaworld008/Commonly-used-high-value-skills. It costs 28 tokens per session (3,634 once invoked), scanned A, original, MIT.

A guide for coordinating software incidents from initial triage through recovery and the later review. It covers severity, timelines, responder roles, communications, mitigations, and post-incident analysis.

In plain words
What is it for?
Use it to classify incidents, assign response roles, prepare stakeholder updates, track mitigations, reconstruct timelines, and create post-incident reviews or runbooks.
Why use it?
During an outage, information and responsibilities can become scattered. A shared response structure helps responders understand impact, coordinate work, and record what happened.

Skill for Claude CodeCodex

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

Good fit Use it to classify incidents, assign response roles, prepare stakeholder updates, track mitigations, reconstruct timelines, and create post-incident reviews or runbooks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/seaworld008/commonly-used-high-value-skills/incident-commander
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 seaworld008/Commonly-used-high-value-skills --skill incident-commander
Clone the repo
git clone --depth 1 https://github.com/seaworld008/Commonly-used-high-value-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-commander

README.md
[![agentmods](https://agentmods.dev/badge/skills/seaworld008/commonly-used-high-value-skills/incident-commander/github.svg)](https://agentmods.dev/skills/seaworld008/commonly-used-high-value-skills/incident-commander)
Your own site
<a href="https://agentmods.dev/skills/seaworld008/commonly-used-high-value-skills/incident-commander"><img src="https://agentmods.dev/badge/skills/seaworld008/commonly-used-high-value-skills/incident-commander/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-commander

Your own site · 80×15
<a href="https://agentmods.dev/skills/seaworld008/commonly-used-high-value-skills/incident-commander"><img src="https://agentmods.dev/badge/skills/seaworld008/commonly-used-high-value-skills/incident-commander.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,634 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00028 $0.03634
Opus 5 $0.00014 $0.01817
Sonnet 5 $0.00006 $0.00727
Haiku 4.5 $0.00003 $0.00363

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

Security

Grade A, and why

incident-commander 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 5d ago.

The scan reads SKILL.md. This mod also ships 6 executable files (scripts/incident_classifier.py, scripts/incident_timeline_builder.py, scripts/pir_generator.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

openclaw-skills/incident-commander/SKILL.md · 486 lines

How it starts

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

Incident Commander Skill

Category: Engineering Team
Tier: POWERFUL
Author: Claude Skills Team
Version: 1.0.0
Last Updated: February 2026

Overview

The Incident Commander skill provides a comprehensive incident response framework for managing technology incidents from detection through resolution and post-incident review. This skill implements battle-tested practices from SRE and DevOps teams at scale, providing structured tools for severity classification, timeline reconstruction, and thorough post-incident analysis.

Key Features

  • Automated Severity Classification - Intelligent incident triage based on impact and urgency metrics
  • Timeline Reconstruction - Transform scattered logs and events into coherent incident narratives
  • Post-Incident Review Generation - Structured PIRs with multiple RCA frameworks
  • Communication Templates - Pre-built templates for stakeholder updates and escalations
  • Runbook Integration - Generate actionable runbooks from incident patterns

Skills Included

Core Tools

  1. Incident Classifier (incident_classifier.py)

    • Analyzes incident descriptions and outputs severity levels
    • Recommends response teams and initial actions
    • Generates communication templates based on severity
  2. Timeline Reconstructor (timeline_reconstructor.py)

    • Processes timestamped events from multiple sources
    • Reconstructs chronological incident timeline
    • Identifies gaps and provides duration analysis
  3. PIR Generator (pir_generator.py)

    • Creates comprehensive Post-Incident Review documents
    • Applies multiple RCA frameworks (5 Whys, Fishbone, Timeline)
    • Generates actionable follow-up items

Incident Response Framework

Severity Classification System

SEV1 - Critical Outage

Definition: Complete service failure affecting all users or critical business functions

Characteristics:

  • Customer-facing services completely unavailable
  • Data loss or corruption affecting users
  • Security breaches with customer data exposure
  • Revenue-generating systems down
  • SLA violations with financial penalties

Read the full file on GitHub · 486 lines

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. 5d ago Changed · -198 lines · -8 tokens per session 352913d93f9e
  2. 9d ago First seen · 684 lines · 36 tokens per session scan A a850d3486960

Subscribe to this mod's changes

incident-commander is a skill published in the GitHub repository seaworld008/Commonly-used-high-value-skills (70 stars, last pushed 5d ago), licensed MIT. It adds 28 tokens to every session and 3,634 once invoked, about $0.0001 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.