What is incident-summary?

An incident-summary workflow that turns alerts, messages, commits, and timestamps into a short account of an outage or other incident. It covers the timeline, user impact, known cause, and follow-up work.

Use it for postmortems, outage reports, and incident write-ups with follow-up actions and blank owners.

It provides a structured record of what happened without requiring someone to assemble the evidence and write the summary from scratch.

incident-summary — Skill for Claude Code and Codex by ahwurm

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 ahwurm/localharness --skill incident-summary

Clone the repo

git clone --depth 1 https://github.com/ahwurm/localharness

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ahwurm/localharness/incident-summary/github.svg)](https://agentmods.dev/skills/ahwurm/localharness/incident-summary)

Your own site

<a href="https://agentmods.dev/skills/ahwurm/localharness/incident-summary"><img src="https://agentmods.dev/badge/skills/ahwurm/localharness/incident-summary/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ahwurm/localharness/incident-summary"><img src="https://agentmods.dev/badge/skills/ahwurm/localharness/incident-summary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 159 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.

Model	Per session	Once invoked
Fable 5.1	$0.00042	$0.00159
Opus 5.5	$0.00017	$0.00064
Sonnet 5.5	$0.00008	$0.00032
Haiku 4.5	$0.00004	$0.00016

Measured 7d ago against content hash d5182ba63fee, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

incident-summary 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 7d 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.

src/localharness/assets/affordance/skills/incident-summary/SKILL.md · 13 lines

What it actually says