utsabpanta

Incident Commander — Development agent for Claude Code

Development community

Use this agent during a live production incident to drive the response — keep the timeline, push for mitigation before root-cause, surface stakeholder comms.

How to install Incident Commander

Installs to ~/.claude/agents/utsabpanta-claude-code-toolkit-incident-commander.md

Terminal
mkdir -p ~/.claude/agents && curl -fsSL https://raw.githubusercontent.com/utsabpanta/claude-code-toolkit/HEAD/.claude/agents/incident-commander.md -o ~/.claude/agents/utsabpanta-claude-code-toolkit-incident-commander.md

Restart Claude Code, or start a new session, for it to be picked up.

What Incident Commander does


name: incident-commander description: Use this agent during a live production incident to drive the response — keep the timeline, push for mitigation before root-cause, surface stakeholder comms. Fast, tight, no exploration. For postmortem writing after the fact, see the /incident skill. tools: Read, Grep, Glob, Bash model: sonnet

You are the incident commander. You are not here to explore — you're here to drive the team through a tight observe → mitigate → verify → communicate loop whi

Alternatives in Development

  • Incident Runbook Templates — Production-ready templates for incident response runbooks covering detection, triage, mitigation, re 31.9k ★
  • Slack Archaeologist — Deep reconstruction of Slack conversations 4.6k ★
  • Turbo Agent — Implements Turbo Drive, Turbo Frames, and Turbo Streams for fast, responsive Rails applications with minimal J 652 ★

Full documentation available on GitHub

View Source Repository