Incident Response

Incident Response is a command for Claude Code from lhfer/claude-howto-zh-cn. It costs 10 tokens per session (81 once invoked), scanned A, original, MIT.

A structured process for handling production incidents, meaning problems affecting a live application or its users. It covers recording the incident, judging its severity and impact, coordinating response, and documenting the outcome.

In plain words
What is it for?
Use it to notify the on-call person, collect diagnostic information, coordinate remediation, record the solution, and schedule a post-incident review.
Why use it?
It gives the team a shared process for responding under pressure and preserving what was learned afterward.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the devops-automation plugin — 4 commands, 3 agents shipped together

Good fit Use it to notify the on-call person, collect diagnostic information, coordinate remediation, record the solution, and schedule a post-incident review.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/lhfer/claude-howto-zh-cn/incident
About the project

Claude Code 中文全面上手指南 is a Chinese-language learning guide for using Claude Code and combining features such as commands, memory, skills, hooks, MCP, subagents, and plugins. It is aimed at Chinese beginners and provides learning paths, examples, and compatibility guidance, while the catalogue entries package parts of that guidance as agent resources.

lhfer/claude-howto-zh-cn · 2,295 stars · on GitHub

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.

Clone the repo
git clone --depth 1 https://github.com/lhfer/claude-howto-zh-cn

Made for: Claude Code.

Or install devops-automation, the plugin that ships this one along with the rest of its 4 commands, 3 agents.

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/commands/lhfer/claude-howto-zh-cn/incident/github.svg)](https://agentmods.dev/commands/lhfer/claude-howto-zh-cn/incident)
Your own site
<a href="https://agentmods.dev/commands/lhfer/claude-howto-zh-cn/incident"><img src="https://agentmods.dev/badge/commands/lhfer/claude-howto-zh-cn/incident/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/commands/lhfer/claude-howto-zh-cn/incident"><img src="https://agentmods.dev/badge/commands/lhfer/claude-howto-zh-cn/incident.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 81 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.00010 $0.00081
Opus 5 $0.00005 $0.00041
Sonnet 5 $0.00002 $0.00016
Haiku 4.5 $0.00001 $0.00008

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

Security

Grade A, and why

Incident Response 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

07-plugins/devops-automation/commands/incident.md · 15 lines

What it actually says

Incident Response / 事故响应

  1. 创建 incident 记录
  2. 判断严重级别和影响面
  3. 通知 on-call
  4. 收集诊断信息
  5. 协调处置
  6. 记录解决方案
  7. 安排 post-mortem
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 · 15 lines · 10 tokens per session scan A dddb8d1e06a5

Subscribe to this mod's changes

Incident Response is a command published in the GitHub repository lhfer/claude-howto-zh-cn (2,295 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 81 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-30.