incident

incident is a command for Claude Code from johnnywuj81/tokenknows. It costs 47 tokens per session (204 once invoked), scanned A, original, MIT.

A command that turns the current troubleshooting or bug-fixing session into a six-part incident review. An incident review records what happened, why it happened, how it was fixed, and what should improve.

In plain words
What is it for?
Use it to document symptoms, impact, root cause, fixes, improvements, and the event timeline, with tags such as incident, bug fix, and severity.
Why use it?
It preserves the investigation and recovery story in a structured form instead of leaving the reasoning scattered across chat messages. A timeline helps show when the failure occurred and how long recovery took.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the tokenknows plugin — 2 skills, 9 commands, 1 MCP server shipped together

Good fit Use it to document symptoms, impact, root cause, fixes, improvements, and the event timeline, with tags such as incident, bug fix, and severity.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/johnnywuj81/tokenknows/incident
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/johnnywuj81/tokenknows

Made for: Claude Code.

Or install tokenknows, the plugin that ships this one along with the rest of its 2 skills, 9 commands, 1 MCP server.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/johnnywuj81/tokenknows/incident"><img src="https://agentmods.dev/badge/commands/johnnywuj81/tokenknows/incident.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 204 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.00047 $0.00204
Opus 5.5 $0.00019 $0.00082
Sonnet 5.5 $0.00009 $0.00041
Haiku 4.5 $0.00005 $0.00020

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

Security

Grade A, and why

incident 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 1mo 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.

tokenknows-plugin/commands/incident.md · 16 lines

What it actually says

按 tokenknows:distill skill 的标准流程,把当前 session 蒸馏成 incident:

incident 关键特征:

  • session 应包含 报警 / 报错 → 排查 → 修复 的完整链
  • 时间线信息很重要 (报警到恢复多久 / MTTR)
  1. 拆 event 时强调时间戳 (occurred_at), 让后端能重建时间线
  2. tag 用 incident / bug_fix / 严重度
  3. submit_session_events
  4. distill_document(document_type="incident", time_window=$ARGUMENTS 默认 last_7_days)
  5. 展示 6 段
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. 1mo ago First seen · 16 lines · 47 tokens per session scan A bddfc6f5caed

Subscribe to this mod's changes

incident is a command published in the GitHub repository johnnywuj81/tokenknows (4 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 204 once invoked, about $0.0002 per session on Opus 5.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.