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 skills/chachamaru127/claude-code-harness/failure-codifiernpx skills add Chachamaru127/claude-code-harness --skill failure-codifiergit clone --depth 1 https://github.com/Chachamaru127/claude-code-harnessWhat 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.00092 | $0.00711 |
| Opus 5 | $0.00046 | $0.00356 |
| Sonnet 5 | $0.00018 | $0.00142 |
| Haiku 4.5 | $0.00009 | $0.00071 |
Grade A, and why
failure-codifier 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 3d 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
Failure Codifier
breezing orchestration ledger + Judgment Ledger から再現失敗を read-only で抽出し、failure-rule.v1 候補を confidence score 付きで提案します。
核心契約
- human-approval-required: codifier は dry-run 提案のみ。
patterns.md/decisions.mdへの自動昇格は構造的に禁止。 - Confidence 閾値: occurrence count ≥ 3 → medium、count ≥ 5 → high（
go/internal/failurecodifier/confidence.go）。 - 昇格先 heuristic:
proposed_ssot_targetフィールドでpatterns.mdまたはdecisions.mdを提案するのみ。
使い方
Dry-run 提案（推奨）
./scripts/failure-codifier-propose.sh --dry-run
stdout は JSON 配列（failure-rule.v1 候補）。SSOT ファイルには一切書き込みません。
Go テスト
cd go && go test ./internal/failurecodifier/... -count=1
参照
- 昇格ワークフロー: references/promotion-workflow.md
- Schema:
templates/schemas/failure-rule.v1.json - Core:
go/internal/failurecodifier/
禁止事項
patterns.md/decisions.mdへの Write / Edit（human 承認後も codifier 経由では不可）AutoPromote/ unattended SSOT 更新- Plans.md の
cc:*マーカー変更
What ships with it
1 file 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.
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.
- 3d ago First seen · 48 lines · 92 tokens per session scan A b57608a39c7c
failure-codifier is a skill published in the GitHub repository Chachamaru127/claude-code-harness (3,079 stars, last pushed 2d ago), licensed MIT. It adds 92 tokens to every session and 711 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…