Borrowing it
Nothing to install: this file belongs to apokamo/kaji. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/apokamo/kaji/main/.claude/skills/incident-fix/SKILL.mdgit clone --depth 1 https://github.com/apokamo/kajiWrote 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/skills/apokamo/kaji/incident-fix)<a href="https://agentmods.dev/skills/apokamo/kaji/incident-fix"><img src="https://agentmods.dev/badge/skills/apokamo/kaji/incident-fix/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.
<a href="https://agentmods.dev/skills/apokamo/kaji/incident-fix"><img src="https://agentmods.dev/badge/skills/apokamo/kaji/incident-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 29 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00081 | $0.00940 |
| Opus 5 | $0.00041 | $0.00470 |
| Sonnet 5 | $0.00016 | $0.00188 |
| Haiku 4.5 | $0.00008 | $0.00094 |
Grade A, and why
incident-fix 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 10d 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 Fix（修正）
直近の査読 RETRY コメントの指摘に対応し、調査 artifact を更新する。incident.yaml では
resume: investigate（調査セッションを継続）で起動される。
収束保証: 指摘対応以外の scope 拡大（新しい調査論点の追加）は行わない。
ワークフロー内の位置: review/verify（RETRY）→ fix → verify
入力
| 変数 | 型 | 説明 |
|---|---|---|
issue_id |
str | 対象インシデントイシュー ID |
issue_ref |
str | 人間可読の Issue 参照 |
step_id |
str | 現在のステップ ID |
cycle_count / max_iterations |
int | サイクル内ステップのため注入される |
resume: investigate により直近査読 verdict の要約が prompt に注入される。手動実行時は
$ARGUMENTS 第 1 トークンを issue_id とする。
共通ルール
.claude/skills/incident-investigate/SKILL.md § 全 incident-* skill 共通ルールに従う。
実行手順
Step 1: 指摘の抽出
artifact root を解決する（共通ルール参照。以降のパスはこの絶対 root 基準）:
ART="$(kaji config artifacts-dir)"
直近の査読 RETRY コメント（verdict マーカー step=review または step=verify の最新）から
指摘リスト（指摘 N）を抽出する:
kaji issue view [issue_id] --comments
Step 2: 指摘への対応
各指摘に対し、以下のいずれかで対応する。
- 追加調査・再実験・artifact 修正: 不足していた citation の追加、再現実験の再試行、 棄却仮説・不足証拠の補強、conclusion の見直し。使い捨て検証環境を使う場合は調査後に破棄する。
- 技術的根拠を示した反論: 指摘が不当と判断する場合、根拠（citation / 再現結果）を添えて反論する。
調査 artifact（$ART/[issue_id]/investigation/report.md）を更新する。新しい調査論点の
追加（scope 拡大）はしない。
Step 3: 対応表のコメント投稿
指摘ごとの対応表（対応 / 反論 / 一部対応）をコメント投稿する。指摘参照は 指摘 N 形式
（auto-close hazard 回避）。verdict マーカーを無条件付与する。
kaji issue comment [issue_id] --commit \
--verdict-step fix --verdict-status <STATUS> \
--body-file <対応報告 markdown>
Verdict 出力
---VERDICT--- status: PASS reason: | 査読指摘に対応し、調査 artifact を更新した evidence: | 指摘 1..N それぞれに対応 / 反論を記録。追加 citation・再現結果を artifact に反映 suggestion: | ---END_VERDICT---
status の選択基準
| status | 条件 |
|---|---|
| PASS | 全指摘に対応 / 反論した（verify で確認へ） |
| ABORT | 前提崩壊（対象が非インシデント等） |
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.
- 10d ago First seen · 87 lines · 81 tokens per session scan A d7118bd23e40
incident-fix is a skill published in the GitHub repository apokamo/kaji (12 stars, last pushed 2d ago), licensed Apache-2.0. It adds 81 tokens to every session and 940 once invoked, about $0.0004 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.
Other skills, from other repositories
superpowers-systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
rust-check
Run cargo check on the current Rust project to find compile errors.
debug
Reproduce, minimize, localize, identify root cause, and distinguish diagnosis from an authorized fix. Prefer root-cause over symptom patches.
langsmith-tracing
LangSmith tracing and debugging setup for LLM applications. Configure observability, capture traces, and enable debugging for LangChain/LangGraph agents.
behavior-contract
Bug condition/postcondition formalization as testable Behavior Contracts. Defines invariants that must be preserved across fixes.
quality-hooks
Language-specific auto-lint/format/typecheck pipeline. Supports Python (ruff+pyright), TypeScript (prettier+eslint+tsc), Go (gofmt+golangci-lint). Auto-fix and convergence loops.