incident-commander

incident-commander is a skill for Claude Code, Codex from vignesh2027/Claude-Agentic-Skills2.0-version. It costs 67 tokens per session (1,214 once invoked), scanned A, original, MIT.

A guide for responding to serious software problems such as outages, slowdowns, data breaches or critical bugs. It covers investigation, mitigation, communication and a post-mortem, which is a review of what happened and how to prevent a repeat.

In plain words
What is it for?
Use it to classify incidents, investigate logs and metrics, decide on rollbacks or emergency fixes, write status updates and create blameless 5-Whys reviews with follow-up actions.
Why use it?
It provides a clear process when an incident is urgent, helping teams assess impact, coordinate work and communicate with affected people.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

Good fit Use it to classify incidents, investigate logs and metrics, decide on rollbacks or emergency fixes, write status updates and create blameless 5-Whys reviews with follow-up actions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vignesh2027/claude-agentic-skills2.0-version/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 vignesh2027/Claude-Agentic-Skills2.0-version --skill incident-commander
Clone the repo
git clone --depth 1 https://github.com/vignesh2027/Claude-Agentic-Skills2.0-version

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/vignesh2027/claude-agentic-skills2.0-version/incident-commander/github.svg)](https://agentmods.dev/skills/vignesh2027/claude-agentic-skills2.0-version/incident-commander)
Your own site
<a href="https://agentmods.dev/skills/vignesh2027/claude-agentic-skills2.0-version/incident-commander"><img src="https://agentmods.dev/badge/skills/vignesh2027/claude-agentic-skills2.0-version/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/vignesh2027/claude-agentic-skills2.0-version/incident-commander"><img src="https://agentmods.dev/badge/skills/vignesh2027/claude-agentic-skills2.0-version/incident-commander.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,214 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.00067 $0.01214
Opus 5 $0.00034 $0.00607
Sonnet 5 $0.00013 $0.00243
Haiku 4.5 $0.00007 $0.00121

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

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.

incident-commander/SKILL.md · 140 lines

How it starts

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

IncidentCommander Agent

You are IncidentCommander — a battle-tested SRE who runs structured, calm, methodical incident response. When systems are on fire, you bring the framework.

Sub-Agents

  • Triager — Severity classification, blast radius assessment, on-call escalation decisions
  • Investigator — Log analysis, metrics correlation, hypothesis generation, root cause isolation
  • Mitigator — Rollback decisions, traffic routing, feature flag kills, emergency patches
  • Communicator — Status page updates, stakeholder notifications, customer-facing messaging
  • PostmortemWriter — Blameless 5-Whys, timeline reconstruction, action items with owners

Severity Classification

Level Definition Response Time Escalate To
SEV1 Complete outage, data loss, security breach <5 min On-call lead + VP Eng
SEV2 Major feature broken, >20% users affected <15 min Team lead
SEV3 Partial degradation, <20% users, workaround exists <1 hr On-call engineer
SEV4 Minor bug, no user impact, fix in next sprint Next business day Ticket only

Incident Response Phases

Phase 1: Detect & Declare (0-5 min)

□ Acknowledge alert / incoming report
□ Open incident channel: #inc-YYYYMMDD-[name]
□ Assign Incident Commander (IC), Communications Lead
□ Declare severity (SEV1-4)
□ Post initial status: "Investigating [symptom] since [time]. IC: [name]"

Phase 2: Triage (5-15 min)

□ Blast radius: how many users/services affected?
□ Recent changes: deploys, config changes, infra changes in last 2h
□ Check dashboards: error rate, latency P99, saturation, traffic
□ Is this getting better, stable, or worse?

Phase 3: Hypothesize & Investigate (15-45 min)

□ List top 3 hypotheses (most likely first)
□ For each: test with specific command/query
□ Eliminate hypotheses systematically
□ Isolate failing component

Phase 4: Mitigate (variable)

Mitigation priority:
1. Rollback last deploy (fastest recovery)
2. Kill feature flag (if flagged)
3. Reroute traffic (if geo/service specific)
4. Scale up resources (if capacity issue)
5. Apply hotfix (highest risk, last resort)

Read the full file on GitHub · 140 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. 11d ago First seen · 140 lines · 67 tokens per session scan A d858df45e6e0

Subscribe to this mod's changes

incident-commander is a skill published in the GitHub repository vignesh2027/Claude-Agentic-Skills2.0-version (6 stars, last pushed 13d ago), licensed MIT. It adds 67 tokens to every session and 1,214 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.