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.
npx agentmods add commands/xcodethink/open-claude-code-skills/incidentgit clone --depth 1 https://github.com/xcodethink/open-claude-code-skillsWrote 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.
[](https://agentmods.dev/commands/xcodethink/open-claude-code-skills/incident)<a href="https://agentmods.dev/commands/xcodethink/open-claude-code-skills/incident"><img src="https://agentmods.dev/badge/commands/xcodethink/open-claude-code-skills/incident.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00026 | $0.00330 |
| Opus 5 | $0.00013 | $0.00165 |
| Sonnet 5 | $0.00005 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
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 4d 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.
What it actually says
incident — 线上事故 triage
用户输入 /incident $ARGUMENTS 触发 4 阶段标准处置流程。
立刻读取并完整加载:
~/.claude/prompts/lib/08-救火/线上事故triage.md
按其"行为契约"段严格执行 4 阶段:
- 止血 5 分钟(rollback / 关 flag / scale up / 降级只读 / status page 五选一)+ 同时通知用户 + 冻结新 deploy + 拉时间线
- 定位 15-30 分钟(看时间线 / 错误流 / 依赖 / 资源 / 形成假设)
- 修复(回滚优先,forward fix 走 bug-fix-standard 加快版)
- 复盘 24-48h 内(incident report:TL;DR + 时间线 + 5 Whys + 处置时间 + action items)
参数含修饰符 → 叠加对应文件。
核心契约:优先止血而非根因分析(根因在第 3 阶段做)。Blameless 复盘,涉及数据泄露立即合规通知。
参数: $ARGUMENTS
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.
- 4d ago First seen · 24 lines · 0 tokens per session scan A 0cf9c775fc51
incident is a command published in the GitHub repository xcodethink/open-claude-code-skills (2 stars, last pushed 29d ago), licensed MIT. It adds 26 tokens to every session and 330 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.
Other commands, from other repositories
go-review
Go code review for idiomatic patterns.
crear-skill
Crear, probar y mejorar skills de forma iterativa. Usa cuando el usuario dice "crear skill", "crear habilidad", "build skill", "create a skill", "skill development", "desarrollar skill", "nueva habilidad". Usa el workflow: draft → test → review → improve → repeat con evaluación cuantitativa y qualitative review.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
cost-tracker
Track session costs, understand token spend, and get optimization tips.
workpm
PM 모드로 오케스트레이터 시작. 팀을 구성하고 5단계 워크플로우로 작업을 완수합니다.
test
Run all PandaFilter verification steps in order. Stop and report on first failure. This is the required pre-commit gate.