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.
npx agentmods add skills/sawrus/agent-guides/incident-commandnpx skills add sawrus/agent-guides --skill incident-commandgit clone --depth 1 https://github.com/sawrus/agent-guidesWrote 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.
[](https://agentmods.dev/skills/sawrus/agent-guides/incident-command)<a href="https://agentmods.dev/skills/sawrus/agent-guides/incident-command"><img src="https://agentmods.dev/badge/skills/sawrus/agent-guides/incident-command.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00024 | $0.01052 |
| Opus 5 | $0.00012 | $0.00526 |
| Sonnet 5 | $0.00005 | $0.00210 |
| Haiku 4.5 | $0.00002 | $0.00105 |
Grade A, and why
incident-command 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.
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.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Incident Command
Expertise: ICS-inspired incident structure, communication templates, mitigation over diagnosis, blameless culture.
When to load
When responding to a P0/P1 incident, coordinating a multi-engineer response, or writing a war room update.
Incident Roles
| Role | Responsibility | Who |
|---|---|---|
| Incident Commander (IC) | Owns coordination; makes go/no-go calls | On-call lead or SRE |
| Technical Lead | Diagnoses and implements fix | On-call engineer |
| Comms Lead | Writes status page + stakeholder updates | PM or secondary on-call |
| Scribe | Documents timeline in real-time | Any available engineer |
P0 Timeline (first 30 minutes)
T+0: ACKNOWLEDGE — "I'm on it" in #incidents Slack
T+2: SCOPE — What's broken? Since when? Who's affected?
→ kubectl get pods -A | grep -v Running
→ Check Grafana error rate + latency dashboard
T+5: PAGE escalation if > 10% users affected or revenue impacted
T+10: STATUS PAGE update: "We are investigating reports of [symptom]"
T+15: MITIGATION — Rollback > fix. Prefer reversible actions.
Order: rollback deploy → feature flag off → scale up → redirect traffic
T+20: COMMUNICATE — Slack update with mitigation status + ETA
T+30: STABILIZE — Confirm metrics returning to baseline
→ Watch error rate for 10 min after mitigation
T+60: PRELIMINARY POSTMORTEM doc created (timeline captured)
T+24h: FULL POSTMORTEM — 5-whys, action items, owners
Mitigation Priority (always prefer fast+reversible)
1. Rollback deploy → helm rollback <release> -n <ns> # < 2 min
2. Feature flag off → LaunchDarkly / split.io toggle # < 1 min
3. Scale up replicas → kubectl scale deploy ... --replicas=N
4. Restart pods → kubectl rollout restart deploy/<n>
5. Redirect traffic → DNS change / load balancer weight
6. Fix forward → only if rollback is not possible
Slack Communication Templates
# P0 Opening Message (#incidents channel)
🔴 **P0 INCIDENT OPEN** — [service] [symptom]
IC: @you | Scribe: @name
Impact: [who is affected, estimated user count]
Current status: Investigating
Thread: all updates in this thread
War room: https://meet.google.com/...
# Update every 15 min until resolved
📊 **UPDATE T+15** — [service]
Status: Mitigating / Resolved / Monitoring
Action taken: Rolled back to v2.3.0
Current error rate: 0.2% (was 8.4%)
ETA: Monitoring for 10 min, then close
# Resolution
✅ **RESOLVED** — [service] — [duration]
Root cause (preliminary): [1-sentence summary]
Mitigation: [what fixed it]
Next: Postmortem within 24h @[owner]
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.
- 5d ago First seen · 120 lines · 24 tokens per session scan A 1e3f198a750e
incident-command is a skill published in the GitHub repository sawrus/agent-guides (17 stars, last pushed 4d ago), licensed MIT. It adds 24 tokens to every session and 1,052 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-08-30.
Other skills, from other repositories
documentation-and-adrs
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
agent-orchestration-improve-agent
Systematic improvement of existing agents through performance analysis, prompt engineering, and continuous iteration.
agentmail
Email infrastructure for AI agents. Create accounts, send/receive emails, manage webhooks, and check karma balance via the AgentMail API.
luna
Reviews code for objective correctness, security, and reliability.
max
Cleans up and improves existing code without changing behavior.
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.