incident-response

incident-response is a skill for Claude Code from hieutrtr/ai1-skills. It costs 97 tokens per session (3,639 once invoked), scanned A, original, no licence file.

Procedures for handling production incidents in Python and React applications. A production incident is a live problem affecting software or its users.

In plain words
What is it for?
Use it during outages, error spikes, performance problems, and post-mortems, including severity classification and incident coordination.
Why use it?
It provides a structured way to classify outages, investigate failures, communicate during them, and review what happened afterward.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it during outages, error spikes, performance problems, and post-mortems, including severity classification and incident coordination.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hieutrtr/ai1-skills/incident-response
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 hieutrtr/ai1-skills --skill incident-response
Clone the repo
git clone --depth 1 https://github.com/hieutrtr/ai1-skills

Made for: Claude Code.

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-response

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

agentmods 80×15 button for incident-response

Your own site · 80×15
<a href="https://agentmods.dev/skills/hieutrtr/ai1-skills/incident-response"><img src="https://agentmods.dev/badge/skills/hieutrtr/ai1-skills/incident-response.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 97 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,639 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown 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.00097 $0.03639
Opus 5 $0.00048 $0.01819
Sonnet 5 $0.00019 $0.00728
Haiku 4.5 $0.00010 $0.00364

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

Security

Grade A, and why

incident-response scanned grade A with 1 finding 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 12d ago.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/fetch-logs.sh, scripts/generate-incident-report.py, scripts/health-check-all-services.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

allowed-tools: Read Grep Glob Write Bash(curl:*) Bash(jq:*)
skills/incident-response/SKILL.md · 409 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Files

What ships with it

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

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. 12d ago First seen · 409 lines · 97 tokens per session scan A 1905eb23920d

Subscribe to this mod's changes

incident-response is a skill published in the GitHub repository hieutrtr/ai1-skills (8 stars, last pushed 7mo ago), with no licence file. It adds 97 tokens to every session and 3,639 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens