incident-commander

incident-commander is a skill for Claude Code from latestaiagents/agent-skills. It costs 74 tokens per session (1,175 once invoked), scanned A, original, MIT.

An incident-response guide for acting as an Incident Commander. An incident is a live outage, service problem, or production failure; the guide defines severity levels, roles, communication, coordination, and timelines.

In plain words
What is it for?
Use it during outages, service degradation, production issues, alerts, or other urgent operational failures.
Why use it?
It gives teams a clear process for deciding what is happening, assigning responsibility, keeping people informed, and restoring service.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the devops-sre plugin — 8 skills, 6 commands shipped together

Good fit Use it during outages, service degradation, production issues, alerts, or other urgent operational failures.

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

Made for: Claude Code.

Or install devops-sre, the plugin that ships this one along with the rest of its 8 skills, 6 commands.

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/latestaiagents/agent-skills/incident-commander/github.svg)](https://agentmods.dev/skills/latestaiagents/agent-skills/incident-commander)
Your own site
<a href="https://agentmods.dev/skills/latestaiagents/agent-skills/incident-commander"><img src="https://agentmods.dev/badge/skills/latestaiagents/agent-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/latestaiagents/agent-skills/incident-commander"><img src="https://agentmods.dev/badge/skills/latestaiagents/agent-skills/incident-commander.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,175 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.00074 $0.01175
Opus 5 $0.00037 $0.00588
Sonnet 5 $0.00015 $0.00235
Haiku 4.5 $0.00007 $0.00118

Measured 10d ago against content hash 994d04509f47, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, 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 10d 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.

plugins/devops-sre/skills/incident-response/incident-commander/SKILL.md · 194 lines

How it starts

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

Incident Commander Guide

Lead incident response with structured communication, clear ownership, and systematic resolution.

Incident Commander Role

The IC (Incident Commander) is responsible for:

  • Coordination: Ensuring right people are engaged
  • Communication: Keeping stakeholders informed
  • Decision-making: Making calls when consensus isn't possible
  • Documentation: Ensuring timeline is captured

The IC does NOT need to be the person fixing the problem.

Incident Severity Levels

Level Description Response Time Examples
SEV1 Critical - Complete outage Immediate Total service down, data loss, security breach
SEV2 Major - Significant impact 15 min Core feature broken, major degradation
SEV3 Minor - Limited impact 1 hour Non-critical feature down, workaround exists
SEV4 Low - Minimal impact Best effort Cosmetic, single user affected

Incident Response Workflow

Phase 1: Detection & Triage (0-5 minutes)

1. Acknowledge the alert
2. Quick assessment:
   - What's broken?
   - Who's affected?
   - What's the blast radius?
3. Assign severity level
4. Declare incident if SEV1/SEV2

Phase 2: Mobilization (5-15 minutes)

1. Create incident channel: #inc-YYYYMMDD-[brief-description]
2. Post initial summary (template below)
3. Page relevant teams if needed
4. Assign roles:
   - IC (Incident Commander) - you or delegate
   - Tech Lead - driving investigation
   - Comms Lead - external communication

Initial Incident Post Template:

🚨 INCIDENT DECLARED

**Severity:** SEV-[X]
**Status:** Investigating
**Impact:** [Who/what is affected]
**Started:** [Time] UTC

**Current Understanding:**
[Brief description of symptoms]

**Roles:**
- IC: @[name]
- Tech Lead: @[name]
- Comms: @[name]

**Next Update:** [Time] (every 15-30 min for SEV1/2)

Phase 3: Investigation (Ongoing)

1. Gather data:
   - Recent deployments?
   - Configuration changes?
   - External dependency issues?
   - Error patterns in logs?
   - Metrics anomalies?

2. Form hypothesis and test

3. Identify mitigation options:
   - Can we rollback?
   - Can we scale?
   - Can we failover?
   - Do we need a hotfix?

Read the full file on GitHub · 194 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. 10d ago First seen · 194 lines · 74 tokens per session scan A 994d04509f47

Subscribe to this mod's changes

incident-commander is a skill published in the GitHub repository latestaiagents/agent-skills (5 stars, last pushed 4mo ago), licensed MIT. It adds 74 tokens to every session and 1,175 once invoked, about $0.0004 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.