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 wyattowalsh/agents --skill incident-response-engineergit clone --depth 1 https://github.com/wyattowalsh/agentsWrote 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/wyattowalsh/agents/incident-response-engineer)<a href="https://agentmods.dev/skills/wyattowalsh/agents/incident-response-engineer"><img src="https://agentmods.dev/badge/skills/wyattowalsh/agents/incident-response-engineer/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/wyattowalsh/agents/incident-response-engineer"><img src="https://agentmods.dev/badge/skills/wyattowalsh/agents/incident-response-engineer.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.00040 | $0.01725 |
| Opus 5.5 | $0.00016 | $0.00690 |
| Sonnet 5.5 | $0.00008 | $0.00345 |
| Haiku 4.5 | $0.00004 | $0.00172 |
Grade A, and why
incident-response-engineer 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 1mo 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Response Engineer
Coordinate production incident response from first signal through recovery and postmortem.
Scope: Live operational incidents and service degradation. NOT for general code review (review), proactive vulnerability scanning (security-scanner), or one-off bug fixing without incident coordination.
Canonical Vocabulary
| Term | Definition |
|---|---|
| severity | Incident priority level based on business impact |
| impact | User-visible harm, revenue loss, or operational degradation |
| blast radius | The systems, regions, tenants, or users affected |
| containment | Short-term action that stops the incident from spreading |
| mitigation | Action that reduces impact before root cause is fully fixed |
| recovery | Restoring the service to accepted operating behavior |
| incident commander | The single coordinator for decisions and timeline |
| stakeholder update | Time-boxed status message for internal or external audiences |
| timeline | Ordered record of facts, decisions, and actions |
| action item | Concrete follow-up with owner and due date |
Dispatch
| $ARGUMENTS | Mode |
|---|---|
triage <signal> |
Classify the incident and establish the first response plan |
stabilize <incident> |
Contain impact and coordinate mitigation |
comms <incident> |
Draft internal or customer-facing updates |
postmortem <incident> |
Build the incident review and corrective actions |
review <timeline or runbook> |
Audit the handling of an incident |
drill <scenario> |
Run a tabletop or rehearsal plan |
| Natural language about a live outage | Auto-detect the closest mode |
| Empty | Show the mode menu with examples |
Mode Menu
| # | Mode | Example |
|---|---|---|
| 1 | Triage | triage elevated 500s in eu-west checkout |
| 2 | Stabilize | stabilize auth outage caused by bad deploy |
| 3 | Comms | comms database failover affecting signups |
| 4 | Postmortem | postmortem queue backlog incident |
| 5 | Review | review incident timeline from 2026-03-12 |
| 6 | Drill | drill primary region outage |
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- evals/evals.json 5.9 KB
- references/comms-templates.md 1.8 KB
- references/containment-recovery-aids.md 2.0 KB
- references/severity-matrix.md 2.0 KB
- references/timeline-postmortem-examples.md 1.7 KB
- scripts/asset_toolkit/__init__.py 303 B runs code
- scripts/asset_toolkit/_shared.py 5.6 KB runs code
- scripts/asset_toolkit/common.py 3.0 KB runs code
- scripts/asset_toolkit/package.py 43 KB runs code
- scripts/asset_toolkit/validate_evals.py 11 KB runs code
- scripts/asset_toolkit/validate_hooks.py 13 KB runs code
- scripts/asset_toolkit/validate_skill.py 3.6 KB runs code
- scripts/check.py 2.2 KB runs code
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.
- 1mo ago First seen · 170 lines · 40 tokens per session scan A cc620a2ebfc0
incident-response-engineer is a skill published in the GitHub repository wyattowalsh/agents (5 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 1,725 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-09-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…