What is root-cause-delivery?

A controlled workflow for taking a reported bug, failure, crash, or substantial code change from an initial report to a checked candidate. It records the case, plan, evidence, and repeated attempts before the work can be closed.

Use it to investigate bugs and regressions, make substantial changes, record evidence, and prepare work that can move toward release.

It prevents a local code change that merely appears fixed from being treated as ready. It requires the observed problem or planned change to be reproduced and checked.

root-cause-delivery — Skill for Claude Code by AnastasiyaW

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.

Any agent

npx skills add AnastasiyaW/codex-claude-code-config --skill root-cause-delivery

Clone the repo

git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config

Made for: Claude Code.

Or install claude-code-config, the plugin that ships this one along with the rest of its 59 skills, 8 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/anastasiyaw/codex-claude-code-config/root-cause-delivery/github.svg)](https://agentmods.dev/skills/anastasiyaw/codex-claude-code-config/root-cause-delivery)

Your own site

<a href="https://agentmods.dev/skills/anastasiyaw/codex-claude-code-config/root-cause-delivery"><img src="https://agentmods.dev/badge/skills/anastasiyaw/codex-claude-code-config/root-cause-delivery/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/anastasiyaw/codex-claude-code-config/root-cause-delivery"><img src="https://agentmods.dev/badge/skills/anastasiyaw/codex-claude-code-config/root-cause-delivery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 94 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,121 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.

Model	Per session	Once invoked
Fable 5.1	$0.00094	$0.02121
Opus 5.5	$0.00038	$0.00848
Sonnet 5.5	$0.00019	$0.00424
Haiku 4.5	$0.00009	$0.00212

Measured today against content hash 0fa339c8932d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

root-cause-delivery 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 today.

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.

skills/development/root-cause-delivery/SKILL.md · 183 lines

How it starts

The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Root-Cause Delivery

The goal is not a green-looking diff. The goal is a candidate that fixes the observed contract and can advance toward release without reopening already proved work.

Use one durable case per substantive incident or code change:

.agent/delivery-cases/<case-id>/
  case.json
  evidence/

The installed root-cause-delivery-guard.py hook records a matching intent from an explicit bug/regression or substantive implementation request. It keeps source edits behind a valid PLAN_FROZEN case and will not allow a changed source tree to close while the case is incomplete. Harness records are never treated as source, so they stay writable before a case is frozen: delivery cases, CONTINUITY.json, .agent/user-tasks/ and transfer contracts (hooks/harness_records.py). A bare background-task <task-notification> records no intent.

Workflow

Create the case before changing source:
```
python ~/.claude/claude-code-config/hooks/root-cause-delivery-guard.py init <case-id> \
  --kind incident --summary "short observed failure"
```
Use --kind change for a feature or non-bug delivery task. The CLI binds the only active prompt intent automatically. If parallel sessions have active intents in the same repository, pass --intent-id <id> shown by the prompt receipt; it refuses to guess which session owns the case.
Fill case.json with observed facts, not a story:
- observed.expected and observed.actual for an incident;
- layer map: entrypoint, owning module, direct dependents, state or contract, tests/probes, and release boundary;
- one causal hypothesis, bounded fix_steps, and a focused verifier argv.
Scope the layer, not the whole repository. The map asks which boundary owns the defect and which direct contracts can break; it is not permission for a speculative rewrite.

For an incident, capture the failing reproducer before source edits:

python ~/.claude/claude-code-config/hooks/root-cause-delivery-guard.py capture <case-id> \
  --phase before -- <exact test command and arguments>

Read the full file on GitHub · 183 lines

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.

today First seen · 183 lines · 94 tokens per session scan A 0fa339c8932d

Subscribe to this mod's changes

root-cause-delivery is a skill published in the GitHub repository AnastasiyaW/codex-claude-code-config (212 stars, last pushed yesterday), licensed MIT. It adds 94 tokens to every session and 2,121 once invoked, about $0.0004 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-10-25.

Debugging LLM Planning ai-agents claude machine-learning prompt-engineering

code-review

Reviews code for bugs, security issues, and best practices.

promptfoo/promptfoo · 11 tokens

trulens-instrumentation

Instrument LLM apps with TruLens OTEL-based tracing - from setup to debugging and optimization.

truera/trulens · 25 tokens

trulens-diagnosis

Diagnose low evaluation scores and generate actionable improvement recommendations.

truera/trulens · 17 tokens

reverse-engineer-anything

Reverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or…

roedyrustam/vibes-plug · 83 tokens

error-resilience-expert

Expert guide for error handling patterns, resilience engineering, retry strategies, circuit breakers, and graceful degradation across React, Next.js, and Node.js / Panduan ahli pola penanganan error, rekayasa ketahanan, strategi retry, circuit breaker, dan degradasi anggun di React, Next.js, dan Node.js.

roedyrustam/vibes-plug · 72 tokens

dependency-upgrade-migrator

Expert guide for dependency upgrades, breaking change migrations, codemod automation, and package audit remediation / Panduan ahli untuk upgrade dependensi, migrasi breaking change, otomasi codemod, dan remediasi audit paket.

roedyrustam/vibes-plug · 52 tokens