Borrowing it
Nothing to install: this file belongs to starmynd-org/infinite-brain-harness. 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/starmynd-org/infinite-brain-harness/main/AGENTS.mdgit clone --depth 1 https://github.com/starmynd-org/infinite-brain-harnessWrote 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/starmynd-org/infinite-brain-harness/agents-md)<a href="https://agentmods.dev/instructions/starmynd-org/infinite-brain-harness/agents-md"><img src="https://agentmods.dev/badge/instructions/starmynd-org/infinite-brain-harness/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.
<a href="https://agentmods.dev/instructions/starmynd-org/infinite-brain-harness/agents-md"><img src="https://agentmods.dev/badge/instructions/starmynd-org/infinite-brain-harness/agents-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.01742 | $0.01742 |
| Opus 5 | $0.00871 | $0.00871 |
| Sonnet 5 | $0.00348 | $0.00348 |
| Haiku 4.5 | $0.00174 | $0.00174 |
Grade A, and why
infinite-brain-harness 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- infinite-brain-harness CLAUDE.md — 94% identical, 17 lines differ
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness (Codex orientation)
This is the Codex mirror of CLAUDE.md. The two files carry the same content and must be edited
together. Orient from this file first.
This is the harness: the shared-parent tier of the Infinite Brain topology, and the folder you open. It
holds no work of its own. Its job is to route your work to the right brain, keep every brain backed up
and synced, and keep an inventory of every repo you run. CLAUDE.md is the Claude Code mirror; keep the
two in sync.
One folder for everything you own: internal/
internal/ holds every repo your own operation owns and operates end to end. It carries two kinds of
child, and the difference is what the harness does with them, not where they sit:
| Kind | What it is | What the harness does |
|---|---|---|
| A mounted brain | Your shared work brain (a company brain, or a department brain that graduated to its own repo) and your individual brain (individual-<your-name>/) |
Clones it in, validates it, registers it, syncs it, and copies its commands up so they work here |
| Any other repo | Product code, client-facing apps, tools: anything you own that is not a brain | Registers it and routes to it. Never mounts it, never copies its commands up |
The harness tells them apart structurally, not from a list: a child is a mounted brain when it
carries both .claude/ and _system/validate.sh, the marker every brain built from the Infinite Brain
OS starter has and no app repo does. A hand-kept list would be wrong the first time a brain was added,
and the failure would be silent: the new brain's commands would simply never appear and nobody would be
told why. It also means an app repo can carry its own .claude/ without leaking commands into this root,
which matters, because plenty of them do.
external/ is the other half of the ownership axis: repos a client owns or that are co-operated with an
outside party, with one client's several repos grouped under external/<group>/. Brains are never
mounted from external/; a client's brain is theirs to mount in their own harness.
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.
- 9d ago First seen · 117 lines · 1,742 tokens per session scan A e528f897d170
infinite-brain-harness AGENTS.md is an instructions file published in the GitHub repository starmynd-org/infinite-brain-harness (23 stars, last pushed 9d ago), licensed MIT. It adds 1,742 tokens to every session, about $0.0087 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
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.