incident-responder

incident-responder is a skill for Claude Code, Codex from puristajs/harness. It costs 16 tokens per session (40 once invoked), scanned A, original, Apache-2.0.

A skill for structuring incident summaries around customer impact, observed evidence, and the next action.

In plain words
What is it for?
Use it to write concise updates after outages, bugs, security events, or other operational incidents.
Why use it?
It keeps incident communication focused on what happened, what is known, and what should happen next.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to write concise updates after outages, bugs, security events, or other operational incidents.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/puristajs/harness/incident-responder
Install

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.

Any agent
npx skills add puristajs/harness --skill incident-responder
Clone the repo
git clone --depth 1 https://github.com/puristajs/harness

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for incident-responder

README.md
[![agentmods](https://agentmods.dev/badge/skills/puristajs/harness/incident-responder/github.svg)](https://agentmods.dev/skills/puristajs/harness/incident-responder)
Your own site
<a href="https://agentmods.dev/skills/puristajs/harness/incident-responder"><img src="https://agentmods.dev/badge/skills/puristajs/harness/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.

agentmods 80×15 button for incident-responder

Your own site · 80×15
<a href="https://agentmods.dev/skills/puristajs/harness/incident-responder"><img src="https://agentmods.dev/badge/skills/puristajs/harness/incident-responder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 40 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00016 $0.00040
Opus 5 $0.00008 $0.00020
Sonnet 5 $0.00003 $0.00008
Haiku 4.5 $0.00002 $0.00004

Measured 11d ago against content hash c512a004b6c3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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 11d 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.

examples/showcase/src/skills/incident-responder/SKILL.md · 11 lines

What it actually says

Prefer concise incident summaries with:

  • customer impact
  • observed evidence
  • next action
Changes

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.

  1. 11d ago First seen · 11 lines · 16 tokens per session scan A c512a004b6c3

Subscribe to this mod's changes

incident-responder is a skill published in the GitHub repository puristajs/harness (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 16 tokens to every session and 40 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-31.