Borrowing it
Nothing to install: this file belongs to gaia-react/gaia. 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/gaia-react/gaia/main/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/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/gaia-react/gaia/claude-md"><img src="https://agentmods.dev/badge/instructions/gaia-react/gaia/claude-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.00627 | $0.00627 |
| Opus 5.5 | $0.00251 | $0.00251 |
| Sonnet 5.5 | $0.00125 | $0.00125 |
| Haiku 4.5 | $0.00063 | $0.00063 |
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 6d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GAIA
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.
- 6d ago Changed · -1 tokens per session f315d51b99ba
- 11d ago Changed · -2 lines · -43 tokens per session 0000e4e8066a
- 15d ago Changed · -2 tokens per session 3e5bbc81e77d
- 21d ago Changed · -31 tokens per session 3380bc641fc1
- 26d ago Changed · +3 lines · +49 tokens per session 082ab382c0ef
- 1mo ago Changed · -13 tokens per session e89285ce5a7e
- 2mo 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 (26 stars, last pushed 4d ago), licensed MIT. It adds 627 tokens to every session, about $0.0025 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-30.
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.