brain-os: Instructions file for Codex

AGENTS.md

brain-os AGENTS.md is an instructions file for Codex, OpenCode from brainOS-HQ/brain-os. It costs 3,348 tokens per session, scanned A, original, MIT.

Repository instructions for Brain OS, an MCP server that stores persistent operational information for AI agents.

In plain words
What is it for?
Answering questions about priorities, decisions, plans, blockers, and focus through Brain OS’s project-state tools.
Why use it?
They tell agents where project state lives and which MCP tools to use instead of treating source code as the answer.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions Claude Code.

This is brainOS-HQ/brain-os's own configuration. It tells Codex and OpenCode how to work on brain-os 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 brain-os configures →

Reuse

Borrowing it

Nothing to install: this file belongs to brainOS-HQ/brain-os. 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/brainOS-HQ/brain-os/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/brainOS-HQ/brain-os

Made for: Codex, OpenCode.

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 brain-os AGENTS.md

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

agentmods 80×15 button for brain-os AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/brainos-hq/brain-os/agents-md"><img src="https://agentmods.dev/badge/instructions/brainos-hq/brain-os/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 3,348 This file is loaded in full into every session.
When invoked 3,348 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.03348 $0.03348
Opus 5.5 $0.01339 $0.01339
Sonnet 5.5 $0.00670 $0.00670
Haiku 4.5 $0.00335 $0.00335

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

Security

Grade A, and why

brain-os 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.

AGENTS.md · 215 lines

How it starts

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

AGENTS.md

Agent operating instructions for the Brain OS repository.

This file is the canonical source of truth for how AI agents (Claude Code, GitHub Copilot, Cursor, Zed, Windsurf, Codex, any MCP-compatible client) should behave when working in this repo. Tool-specific files (CLAUDE.md, .github/copilot-instructions.md, .cursor/rules/brain-os.mdc) are thin pointers to this document.


Context

This repo IS Brain OS — an MCP server for persistent operational state across AI agents. State lives in .brain/. The MCP server is built from src/, published to npm as brain-os, and exposes tools prefixed mcp__brain-os__* when connected as a client.

When asked about project state, priorities, decisions, plans, blockers, or focus, you are answering questions about an operating product, not a codebase. Use the MCP tools. Do not grep source code.


The hard rule

For ANY question about project state, priorities, decisions, patterns, focus, or what to work on, use the Brain OS MCP tools as the primary data source. Never read src/tools/focus-get.ts (or similar) to answer "what should I focus on" — that's the implementation of the tool, not the answer. Call the tool itself.

If you read source code as your first action on a state question, you are in generic-coding-assistant mode. Stop and re-route through MCP.


Tool routing (in order)

# Tool When to call
1 mcp__brain-os__entity_read(entity_id?) First call for ordinary project-state questions. Omit entity_id to list all entities.
2 mcp__brain-os__plan_read(entity_id) Get active step + progress for an entity.
3 mcp__brain-os__context_resolve(user_message?, files_touched?, explicit_entity_id?) Resolve context before focus_get / decision_check when the target entity is not already known. For "what should I work on" from inside a workspace, call this before focus_get.
4 mcp__brain-os__project_evidence_scan(root_path, entity_id?) Read-only repo evidence (STATE.md, FLAGS*, HANDOFF*, ROADMAP/PLAN/TODO, git activity, dirty files). Call AFTER context_resolve and BEFORE focus_get when a workspace path is known. NOT a router — never use it to pick the project.
5 mcp__brain-os__focus_get(entity_id?, constraints?) Prioritized recommendations. Pass resolved entity_id to scope to one project; omit only for explicit global focus or unresolved context.
6 mcp__brain-os__semantic_recall(query, source_kind?) Fuzzy search when you don't know the entity ID or want cross-decision / pattern / session context.
7 mcp__brain-os__decision_check(proposed_action, entity_id?) Call before any action that might contradict an active decision. Returns clear / caution / conflict, plus review_triggered — decisions whose invalidate_if condition the action matches (premise may have changed; surface for review, don't enforce).
8 mcp__brain-os__pattern_detect() Surface current behavioral patterns.
9 mcp__brain-os__entity_update, plan_update, decision_log, decision_refresh, memory_commit Mutating tools. Use when writing state back.

Read the full file on GitHub · 215 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. 1mo ago First seen · 215 lines · 3,348 tokens per session scan A cf15478e7b04

Subscribe to this mod's changes

brain-os AGENTS.md is an instructions file published in the GitHub repository brainOS-HQ/brain-os (6 stars, last pushed 8d ago), licensed MIT. It adds 3,348 tokens to every session, about $0.0134 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,786 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,731 tokens

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.

denoland/deno · 3,077 tokens