Borrowing it
Nothing to install: this file belongs to u9401066/rootcause-mcp. 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/u9401066/rootcause-mcp/master/AGENTS.mdgit clone --depth 1 https://github.com/u9401066/rootcause-mcpWrote 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/instructions/u9401066/rootcause-mcp/agents-md)<a href="https://agentmods.dev/instructions/u9401066/rootcause-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/u9401066/rootcause-mcp/agents-md/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/instructions/u9401066/rootcause-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/u9401066/rootcause-mcp/agents-md.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.01742 | $0.01742 |
| Opus 5.5 | $0.00697 | $0.00697 |
| Sonnet 5.5 | $0.00348 | $0.00348 |
| Haiku 4.5 | $0.00174 | $0.00174 |
Grade A, and why
rootcause-mcp AGENTS.md 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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RootCause MCP Clinical Reasoning Harness
These are the workspace instructions for agents developing or using RootCause MCP to turn multiple de-identified clinical records into an evidence-grounded differential diagnosis and medical root-cause analysis.
Goal
Produce one auditable case package with source lineage, canonical timeline, competing DDx, Bayesian evidence links, cognitive audit, Fishbone/Why/HFACS analysis, conservative causation status, limitations, and qualified-human review state.
Working style
- Use Traditional Chinese unless the user requests another language.
- For clinician-facing prose, keep canonical diagnosis, test, drug, and procedure names in English. On first use, an established abbreviation may be written with an optional Traditional Chinese gloss; never invent a translation or expand an ambiguous abbreviation.
- Treat the system as retrospective decision support, never an autonomous diagnostic or treatment system.
- Separate source observations, host extraction, clinical interpretation, hypotheses, and causal claims.
- Treat
unknown,unverified, andinsufficient dataas reasoning inputs: state which mechanisms remain open and what evidence would discriminate them instead of turning missingness into a negative finding. - Never fabricate a probability or likelihood ratio. An uncalibrated compatibility default is an implementation placeholder, not clinical probability, rank, or certainty.
- Keep updates concise and state which workflow gate is complete or blocked.
Required harness
For case analysis, handoff, prompt/resource design, or agent integration, read:
.codex/skills/rootcause-clinical-reasoning-harness/SKILL.md.codex/skills/rootcause-clinical-reasoning-harness/references/case-handoff.md.codex/skills/rootcause-clinical-reasoning-harness/references/clinician-ddx-discussion-zh-tw.mdwhen writing a clinician-facing DDx discussionclinical://contracts/case-input-manifestclinical://contracts/case-analysis-report
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 · 92 lines · 1,742 tokens per session scan A 778d0106eae4
rootcause-mcp AGENTS.md is an instructions file published in the GitHub repository u9401066/rootcause-mcp (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 1,742 tokens to every session, about $0.0070 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-08-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.