OpenOnco: Instructions file for Claude Code

CLAUDE.md

OpenOnco CLAUDE.md is an instructions file for Claude Code from romeo111/OpenOnco. It costs 3,558 tokens per session, scanned A, original, MIT.

Repository instructions for OpenOnco, a public oncology clinical decision-support project. The project uses a patient's profile to produce two treatment plans with source citations, while its specifications define which documents are authoritative.

In plain words
What is it for?
Use them when changing OpenOnco's rule engine, data, documentation, or rendering code. They explain the source-of-truth order, repository layout, and important project constraints.
Why use it?
They help agents avoid outdated material and keep changes aligned with the project's governance and clinical rules. This matters because the software deals with treatment information.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code; mentions Codex.

This is romeo111/OpenOnco's own configuration. It tells Claude Code how to work on OpenOnco itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything OpenOnco configures →

Reuse

Borrowing it

Nothing to install: this file belongs to romeo111/OpenOnco. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/romeo111/OpenOnco/master/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/romeo111/OpenOnco

Made for: Claude Code.

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.

agentmods badge for OpenOnco CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/romeo111/openonco/claude-md/github.svg)](https://agentmods.dev/instructions/romeo111/openonco/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/romeo111/openonco/claude-md"><img src="https://agentmods.dev/badge/instructions/romeo111/openonco/claude-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.

agentmods 80×15 button for OpenOnco CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/romeo111/openonco/claude-md"><img src="https://agentmods.dev/badge/instructions/romeo111/openonco/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 3,558 This file is loaded in full into every session.
When invoked 3,558 The same file — it is already loaded in full.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.03558 $0.03558
Opus 5.5 $0.01423 $0.01423
Sonnet 5.5 $0.00712 $0.00712
Haiku 4.5 $0.00356 $0.00356

Measured 19d ago against content hash ce0495284a30, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

OpenOnco CLAUDE.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 19d 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.

CLAUDE.md · 295 lines

How it starts

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

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) and similar AI agents (Codex, etc.) when working in this repository. Read this file in full at the start of every session.

Project: OpenOnco

Free public resource for oncology clinical decision support. User uploads a patient profile → receives two alternative treatment plans (standard + aggressive) with full source citations. Plans refresh as new data arrives (new labs, doctor decisions, updated guidelines).

Documentation snapshot: 2026-10-10. Latest tagged software release: v0.1.3; the deployed website also includes later master changes. Browser engine, Onco Wiki, Handbook (English MVP), bilingual site navigation and a synthetic DLBCL review packet are available. Clinical content remains provisional according to entity review status. See README.md, docs/DEVELOPMENT.md and docs/SEARCH_INDEXING.md for current usage and delivery details.

Source of truth hierarchy

When instructions conflict, obey this order:

  1. specs/CHARTER.md — project governance + scope
  2. Other specs/*.md — clinical, data, schema, source, reference case
  3. This CLAUDE.md
  4. README.md
  5. Anything under legacy/ — not authoritative; historical reference only

legacy/ contains the pre-OpenOnco autoresearch pipeline. Retired (not deleted) because the LLM-ranks-treatments pattern conflicts with CHARTER §8.3. Don't use it as a pattern for new work.

Repo layout (top level)

cancer-autoresearch/
├── specs/                            # active specifications (UA)
├── knowledge_base/
│   ├── clients/                      # SourceClient implementations
│   │   ├── ctgov_client.py           # ClinicalTrials.gov v2
│   │   ├── pubmed_client.py
│   │   ├── dailymed_client.py
│   │   ├── openfda_client.py
│   │   └── translate_client.py
│   ├── engine/                       # rule engine + render + MDT
│   │                                 # actionability_{types,client,extract,conflict}.py
│   ├── schemas/                      # Pydantic entity schemas
│   ├── validation/                   # YAML loader + validators
│   ├── ingestion/                    # МОЗ extractor, civic_loader.py, ...
│   └── hosted/
│       ├── content/                  # KB YAML data (diseases, regimens, RFs, …)
│       └── civic/<date>/             # CIViC nightly snapshot (CC0)
├── docs/                             # built site (openonco.info) + reviews/
├── scripts/                          # build_site.py, fill scripts, coverage tools
├── tests/                            # pytest suite
├── legacy/                           # retired autoresearch pipeline (not authoritative)
├── README.md
└── CLAUDE.md

Read the full file on GitHub · 295 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.

  1. 19d ago Changed · +17 lines · +190 tokens per session ce0495284a30
  2. 20d ago Changed · +3 lines · +44 tokens per session 94a0c4ef3e9b
  3. 2mo ago First seen · 275 lines · 3,324 tokens per session scan A 4ae1d01bddf2

Subscribe to this mod's changes

OpenOnco CLAUDE.md is an instructions file published in the GitHub repository romeo111/OpenOnco (2 stars, last pushed today), licensed MIT. It adds 3,558 tokens to every session, about $0.0142 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.

Related

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,461 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,750 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens