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 skills add juanmhidalgo/claude-plugins --skill incident-responsegit clone --depth 1 https://github.com/juanmhidalgo/claude-pluginsWrote 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/juanmhidalgo/claude-plugins/incident-response)<a href="https://agentmods.dev/skills/juanmhidalgo/claude-plugins/incident-response"><img src="https://agentmods.dev/badge/skills/juanmhidalgo/claude-plugins/incident-response/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.
<a href="https://agentmods.dev/skills/juanmhidalgo/claude-plugins/incident-response"><img src="https://agentmods.dev/badge/skills/juanmhidalgo/claude-plugins/incident-response.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00047 | $0.01831 |
| Opus 5.5 | $0.00019 | $0.00732 |
| Sonnet 5.5 | $0.00009 | $0.00366 |
| Haiku 4.5 | $0.00005 | $0.00183 |
Grade A, and why
incident-response 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 2mo 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Response
Run an incident through three phases: new (triage) → update (status broadcast) → postmortem (blameless retrospective).
When to use this vs. debugging-strategies
- Incident response: production is degraded, multiple users affected, time-pressured, multi-actor coordination needed.
- debugging-strategies: a bug in your local environment or CI, single engineer working through it.
If you started in debugging-strategies and it escalated into a customer-impacting outage, switch here. The mindset shifts from "find the cause" to "stop the bleeding, then find the cause." The actual investigation work still uses debug:debugging-strategies — this skill is the coordination layer on top.
Mode 1 — new: Triage
Detect, classify severity, assign roles. The first 5 minutes set the trajectory.
Severity Classification
| Level | Criteria | Response |
|---|---|---|
| SEV1 | Service down for all users / data loss in progress / security breach | Immediate; all-hands; page incident commander |
| SEV2 | Major feature degraded for many users / persistent errors on critical paths | Within 15 min; assign IC and comms |
| SEV3 | Minor feature issue for some users / non-critical degradation | Within 1 hour; one responder |
| SEV4 | Cosmetic / low-impact / single-user issue | Next business day; ticket |
Triage Output Template
# Incident: <title>
**Severity**: SEV<X>
**Detected**: <timestamp> **Detected by**: <alert / customer / oncall>
**Affected**: <users / regions / features>
## Initial Hypothesis
<one paragraph — what we currently think is happening, with confidence>
## Roles
- **Incident Commander**: <name>
- **Communications**: <name>
- **Responders**: <names>
## Immediate Actions
- [ ] <stop-the-bleeding step>
- [ ] <containment step>
- [ ] <data-collection step (logs, metrics, repro)>
Mode 2 — update: Status Broadcast
Post regular updates to keep stakeholders informed. Cadence:
- SEV1: every 15 minutes minimum
- SEV2: every 30 minutes
- SEV3: every 1 hour or on status change
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.
- 2mo ago First seen · 175 lines · 47 tokens per session scan A 5fa9e58adacc
incident-response is a skill published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 1,831 once invoked, about $0.0002 per session on Opus 5.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.
incident-response compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| incident-responsejuanmhidalgo/claude-plugins | Skill | 8 | yesterday | MIT | A | 47 | Claude Code |
| incident-responseorlando-japan/claude-code-setting | Skill | 2 | 1mo ago | MIT | A | 36 | Claude Code, Codex |
| incident-postmortemcamilooscargbaptista/cto-toolkit | Skill | 8 | 7mo ago | MIT | A | 134 | Claude Code |
| incident-response-skillagentfront/frontmcp | Skill | 148 | yesterday | Apache-2.0 | A | 24 | Claude Code, Codex |
| azure-diagnosticsseaworld008/Commonly-used-high-value-skills | Skill | 74 | 2d ago | MIT | A | 22 | Claude Code, Codex |
| vigil-incidenttonone-ai/tonone | Skill | 77 | 23d ago | MIT | A | 48 | Claude Code |
| kubectl-investigatoranyshift-io/sre-skills | Skill | 17 | 9d ago | Apache-2.0 | A | 159 | Claude Code |