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/gaia-react/gaia/claude-mdgit clone --depth 1 https://github.com/gaia-react/gaiaWrote 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/gaia-react/gaia/claude-md)<a href="https://agentmods.dev/instructions/gaia-react/gaia/claude-md"><img src="https://agentmods.dev/badge/instructions/gaia-react/gaia/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.00668 | $0.00668 |
| Opus 5 | $0.00334 | $0.00334 |
| Sonnet 5 | $0.00134 | $0.00134 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
gaia 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.
How it starts
The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GAIA React
Response style
Terse in conversation: lead with the verdict, telegraphic phrasing welcome, no filler, preamble, or validation. Keep caveats short and spend the response on the main answer. Explain at a high level unless depth is asked for. Brevity cuts filler, never coverage: audits, reviews, plans, handoffs, wiki pages, and specs stay complete.
Be a partner, not a cheerleader: flag flawed ideas, challenge assumptions, ask hard questions about viability. Coach as well as critique: explain the why, offer the better pattern.
Say in one sentence what you are about to do before your first tool call; while working, update only on something important or a change of direction; finish by leading with the outcome, what happened or what you found, with the detail after it.
Before responding
The failure mode is reactivity: turning a stimulus into a response without first characterizing the stimulus. Four triggers, one question each before sending.
Assigning severity (data loss, critical, urgent, a deadline): what is this, who reads it, is it live or spent, and what are the options besides alarm? Characterize first, then rate.
Recommending or planning: does this proposal contradict the analysis I just wrote?
Acting to prevent a risk: does the risk apply here, on this timescale? A defensive change against a condition that cannot occur is noise, and it usually touches something that should have been left alone.
Generalizing an instruction: did they say this, or am I extending it? Name the warrant. A narrow instruction is not a mandate.
Reactivity is biased toward action: more alarm, more fixes, more scope, never less. The tell is being about to do something.
Wiki and memory
wiki/ is the committed, shared knowledge base for architecture and dev practices. The machine-local auto-memory is neither committed nor visible to other developers, so durable knowledge goes to wiki/ or .claude/rules/ and only machine-local prefs stay in memory.
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 · 40 lines · 668 tokens per session scan A 3439fe8dd68d
gaia CLAUDE.md is an instructions file published in the GitHub repository gaia-react/gaia (23 stars, last pushed today), licensed MIT. It adds 668 tokens to every session, about $0.0033 per session on Opus 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-30.
Other instructions, from other repositories
react-native CLAUDE.md
Claude Code instructions for storybookjs/react-native, covering development commands, initial setup, development, story generation and testing.
react-seed AGENTS.md
Instructions for guokaigdg/react-seed, covering agents.md, 目录, 1. 项目概览, 2. 技术栈 and 3. 目录结构.
vite-ts-react-template architecture.instructions.md
Instructions for bartstc/vite-ts-react-template, covering architecture rules, project structure, feature slice layers, dependency rule and additional rules.
vite-ts-react-template code-style.instructions.md
Instructions for bartstc/vite-ts-react-template, covering code style, file naming, typescript, react and general.
vite-ts-react-template workflow.instructions.md
Instructions for bartstc/vite-ts-react-template, covering workflow, scanning repository, anchor comments and implementation.
comet AGENTS.md
AGENTS.md instructions for MetroStar/comet, covering comet, project structure, development guidelines, styling guidelines and unit testing.