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 skills add yogsoth-ai/de-anthropocentric-research-engine --skill drill-root-causesgit clone --depth 1 https://github.com/yogsoth-ai/de-anthropocentric-research-engineWrote 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/yogsoth-ai/de-anthropocentric-research-engine/drill-root-causes)<a href="https://agentmods.dev/skills/yogsoth-ai/de-anthropocentric-research-engine/drill-root-causes"><img src="https://agentmods.dev/badge/skills/yogsoth-ai/de-anthropocentric-research-engine/drill-root-causes/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/yogsoth-ai/de-anthropocentric-research-engine/drill-root-causes"><img src="https://agentmods.dev/badge/skills/yogsoth-ai/de-anthropocentric-research-engine/drill-root-causes.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00024 | $0.00463 |
| Opus 5.5 | $0.00010 | $0.00185 |
| Sonnet 5.5 | $0.00005 | $0.00093 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
drill-root-causes 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.
What it actually says
drill-root-causes
Purpose
Move from symptoms to causal structure using complementary root-cause representations and validity checks.
Input contract
required: [symptoms_or_undesirable_effects]
optional: [evidence, system_boundary, known_causes]
constraints: [each causal edge needs an evidence or assumption label]
Execution protocol
Do not perform called SOP operations inline; each loaded SOP owns its contract and thresholds.
- You MUST load skill
drill-five-whysto drill repeated whys. - You MUST load skill
decompose-ishikawato decompose six causal categories. - You MUST load skill
build-current-reality-treeto build the current-reality tree. - You MUST load skill
validate-causal-linkto validate its causal links. If the root-cause chain depends on untested assumptions, considerassumption-stress-testas the next tactic. Deviation: use fewer representations only when the input explicitly limits scope; record omitted views and reason.
Output contract
produces: [why_chain, ishikawa_map, current_reality_tree, root_cause_set]
delta_fields: [findings, assumption_updates, uncertainties, decisions, open_questions]
Thresholds and quality gates
- B: at least one symptom-to-root path is represented in each selected model; every retained edge is checked for direction and support.
Failure and counterexamples
Do not call a correlation a root cause, or stop at a label that cannot explain the observed effects.
Provenance map
root-cause-drilling,causal-tree-building,five-whys-drilling,ishikawa-decomposition,current-reality-tree: resolved/concept per exact lookup.- Status: all five exact names resolved.
Preserved source criteria ledger
- Preserve five-whys, 6M Ishikawa, TOC current-reality-tree, and causal-link validation.
Context checkpoint / Delta notes
Append symptom changes, causal edges, competing roots, and validation failures.
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.
- 1mo ago First seen · 40 lines · 24 tokens per session scan A c548865d03d5
drill-root-causes is a skill published in the GitHub repository yogsoth-ai/de-anthropocentric-research-engine (505 stars, last pushed yesterday), licensed Apache-2.0. It adds 24 tokens to every session and 463 once invoked, about $0.0001 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-09-24.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…