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 OneWave-AI/claude-skills --skill incident-respondergit clone --depth 1 https://github.com/OneWave-AI/claude-skillsWrote 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/onewave-ai/claude-skills/incident-responder)<a href="https://agentmods.dev/skills/onewave-ai/claude-skills/incident-responder"><img src="https://agentmods.dev/badge/skills/onewave-ai/claude-skills/incident-responder/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/onewave-ai/claude-skills/incident-responder"><img src="https://agentmods.dev/badge/skills/onewave-ai/claude-skills/incident-responder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00072 | $0.01048 |
| Opus 5 | $0.00036 | $0.00524 |
| Sonnet 5 | $0.00014 | $0.00210 |
| Haiku 4.5 | $0.00007 | $0.00105 |
Grade A, and why
incident-responder 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 9d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Responder
Act as an expert SRE and production incident responder. Systematically investigate, diagnose, classify, and guide an incident through resolution, then produce actionable reports, audience-specific communications, and a prevention-focused post-mortem.
Core Principles
- Speed over perfection: during an active incident, fast triage beats thorough analysis.
- Evidence-based diagnosis: back every conclusion with log entries, metrics, deploy diffs, or config changes. Never guess.
- Clear communication: write each output for its audience. Engineers get technical detail, executives get business impact, customers get reassurance and ETAs.
- Blameless culture: focus post-mortems on systems and processes, never individuals.
- Prevention orientation: include both immediate fixes and long-term prevention in every remediation.
Contents
references/severity-matrix.md-- SEV1-4 classification criteria, response expectations, escalation/de-escalation rules.references/investigation-protocol.md-- log sources, deploy checks, dependency and resource analysis, root cause chain, codebase patterns.references/diagnostic-commands.md-- shell commands for logs, resources, containers, databases, git history.references/communication-templates.md-- status page, internal, executive, and customer-facing templates.references/incident-report-template.md-- fullincident-report.mdstructure.references/escalation-and-status.md-- escalation paths, IC responsibilities, status page cadence and rules.references/checklists.md-- declaration, verification, resolution, and post-mortem checklists.
Workflow
-
Gather context. Ask what is broken, when it started, who is affected, what changed recently, whether a workaround exists, and whether the issue is ongoing. Search the codebase for the affected service, check git log for recent deploys, and locate relevant log files and monitoring config.
-
Classify severity. Apply the matrix in
references/severity-matrix.md, taking the highest level matched by any criterion. State the classification, its implications, and the required response cadence.
What ships with it
7 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.
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.
- 9d ago First seen · 58 lines · 72 tokens per session scan A 455e2fa2afcc
incident-responder is a skill published in the GitHub repository OneWave-AI/claude-skills (291 stars, last pushed 1mo ago), licensed MIT. It adds 72 tokens to every session and 1,048 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
lcx-report-bug
Create a high-signal bug issue or PR in the repo that owns the defect. Use this whenever the user asks to report, file, open, or triage a LazyCodex, lazycodex-ai, omo-codex, Codex plugin, or upstream Codex CLI bug, especially when they need source-backed root cause, reproduction steps, fix guidance, and GitHub routing.
ast-grep
Searches and rewrites code by AST shape across 25 languages. Use when the target is a syntax pattern (every call/class/import shaped like X, a codemod, a YAML rule) rather than literal text; for plain strings, comments, or filenames, use rg.
debugging
Runs a hypothesis-driven debugging loop across any language or binary, escalating to orthogonal oracle angles and locking the fix with a failing test. Use for crashes, silent failures, hangs, wrong responses, memory leaks, async misbehavior, or reverse engineering.
lcx-doctor
Diagnose LazyCodex and Codex CLI installation health against the latest sources. Use whenever the user asks for a doctor or health check, says LazyCodex, lazycodex-ai, omo-codex, or Codex behaves oddly after an install, update, or config change, suspects a stale, drifted, or broken setup, or wants the local install…
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits. Triggers: remove dead code, dead code, cleanup, remove unused.
lsp
Use when Codex needs language-server diagnostics, definitions, references, symbols, or rename safety checks in the current workspace.