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 instructions/projectdxai/labrat/claude-mdgit clone --depth 1 https://github.com/ProjectDXAI/labratWrote 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/projectdxai/labrat/claude-md)<a href="https://agentmods.dev/instructions/projectdxai/labrat/claude-md"><img src="https://agentmods.dev/badge/instructions/projectdxai/labrat/claude-md.svg" alt="Measured on agentmods" 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 | $0.00619 | $0.00619 |
| Opus 5 | $0.00309 | $0.00309 |
| Sonnet 5 | $0.00124 | $0.00124 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
labrat 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 4d 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.
This is a copy
92% identical to labrat AGENTS.md — 13 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
labrat repo
This is the repository root, not a runnable lab directory.
Use this file when working on labrat itself from Claude Code.
If Claude Code is opened inside a nested lab that has its own CLAUDE.md, follow the lab-local file for runtime operation. This root file governs repo maintenance, scaffold consistency, releases, and docs.
Source Of Truth
- Product/setup docs:
README.md,program.md,docs/getting-started.md,docs/runners.md,docs/MODEL_GUIDANCE.md - Scaffolded lab UX:
templates/AGENTS.md,templates/CLAUDE.md,templates/.agents/skills/,templates/.claude/commands/,templates/agent_prompts/ - Canonical example lab:
examples/nlp-sentiment/research_lab/ - Packaging/versioning:
pyproject.toml,labrat/__init__.py,CHANGELOG.md
Interface Rules
- Keep Claude Code and Codex first-class. If a lab gets one operator surface, add the matching one for the other interface.
- Generated labs should ship
AGENTS.md,.agents/skills/,CLAUDE.md,.claude/commands/, andagent_prompts/. - Keep
CLAUDE.mddurable and command-focused. Put shared phase details inagent_prompts/. - Do not require a hidden local setup for basic operation. The runnable contract should live in the repo.
- When operator guidance changes, keep templates, the canonical example lab, and the docs in sync.
- Prefer
labrat ...examples in docs when working from the repo root. Keep the copiedscripts/*.pyflow valid inside labs.
Frontier Model Rules
- Use
docs/MODEL_GUIDANCE.mdfor model and prompt-process updates. - GPT-5.5 is a Codex host selection, not a lab runtime constant. Do not hardcode API model IDs into
labratfor Codex usage. - Prefer explicit completion and verification contracts over broad encouragement.
- Reserve high reasoning effort for design, audit, frame break, profile authoring, and release work.
Checks
. .venv/bin/activate && labrat doctor --lab-dir examples/nlp-sentiment/research_lab. .venv/bin/activate && labrat next-prompt --lab-dir examples/nlp-sentiment/research_lab --runner claude --phase auto. .venv/bin/activate && labrat next-prompt --lab-dir examples/nlp-sentiment/research_lab --runner codex --phase auto. .venv/bin/activate && make smoke
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.
- 4d ago First seen · 44 lines · 619 tokens per session scan A 70fa6de9c21c
labrat CLAUDE.md is an instructions file published in the GitHub repository ProjectDXAI/labrat (239 stars, last pushed 27d ago), licensed MIT. It adds 619 tokens to every session, about $0.0031 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to labrat AGENTS.md, differing in 13 lines, and is treated as a copy.
Other instructions, from other repositories
Svatah CLAUDE.md
Instructions for bayeslabs-rsi/Svatah, covering svatah, architecture overview, key concepts, workspace & state and experiment lifecycle.
agentic-rd-skill AGENTS.md
AGENTS.md instructions for TheStreamCode/agentic-rd-skill, covering repository instructions, purpose and sources of truth, repository invariants, implementation style and documentation synchronization.
solo AGENTS.md
AGENTS.md instructions for solo-agent/solo, covering project testing rules and project service lifecycle rules.
research-os AGENTS.md
Instructions for lxinfei5/research-os, covering researchos — constitution, §0 what this is, §1 directory discipline, §2 half-life (innovation 1) — memory design and §3 behavior pillars (innovations 2–5).
AI-System-Design-Consultant CLAUDE.md
Claude Code instructions for deepanshu2711/AI-System-Design-Consultant, covering claude.md, what this is, running it, load-bearing typos — do not "fix" these paths and agent node pattern.
agent-eve CLAUDE.md
Instructions for shehryarsaroya/agent-eve, covering claude.md — agent eve (né the compact, then agent transfer), 0. 🚨 hard rules, 1. what this is, 2. doc map and 3. state of play (2026-07-26).