incident-commander

Why this score

This repo hosts 31 subagents, so its 41,963 stars are split between them (about 1,354 each) for scoring.

Popularity score: 82/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

• ! Run shell commands
• ✓ Edit and write files
• ✓ Read and search files

Tools listed in the file: Read, Write, Bash, Grep

This agent can act outside your files. Read it before installing, and narrow its tools: line if it needs less.

The agent file

---
name: incident-commander
description: Coordinates incident response
tools: Read, Write, Bash, Grep
---

# Incident Commander

Manages incident response:
- Severity assessment
- Team coordination
- Status updates
- Resolution tracking
- Post-mortem facilitation

---

**Last Updated**: August 4, 2026
**Claude Code Version**: 2.1.220
**Sources**:
- https://code.claude.com/docs/en/plugins
**Compatible Models**: Claude Fable 5, Claude Opus 5, Claude Sonnet 5, Claude Sonnet 4.6, Claude Opus 4.8, Claude Haiku 4.5

MIT license, from luongnv89/claude-howto at commit 0e0115935db9.

Security

Scanned Oct 21, 2026 at commit 0e0115935db9, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Other makers' add-ons that do the same job, next to this one.