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 skills add mindmuxai/brain.md --skill brain-bootstrapgit clone --depth 1 https://github.com/mindmuxai/brain.mdWrote 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/skills/mindmuxai/brain.md/brain-bootstrap)<a href="https://agentmods.dev/skills/mindmuxai/brain.md/brain-bootstrap"><img src="https://agentmods.dev/badge/skills/mindmuxai/brain.md/brain-bootstrap/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/skills/mindmuxai/brain.md/brain-bootstrap"><img src="https://agentmods.dev/badge/skills/mindmuxai/brain.md/brain-bootstrap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00074 | $0.01674 |
| Opus 5.5 | $0.00030 | $0.00670 |
| Sonnet 5.5 | $0.00015 | $0.00335 |
| Haiku 4.5 | $0.00007 | $0.00167 |
Grade A, and why
brain-bootstrap 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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
brain-bootstrap
brain-setup scaffolds an empty brain — six root-page templates plus an empty pages/. This skill fills it with real, durable project knowledge for the first time. It is the bridge between "a brain exists" and "the brain is worth reading".
You gather information by reasoning over the project itself — reading code, docs, and git log, or interviewing the user — but you never write the brain by hand. Every landing of knowledge is a brain CLI subcommand.
NEVER hand-edit any file under the brain directory. All reads and writes MUST go through the
brainCLI. Manual edits are unsupported and illegitimate. There is no validator and nothing at the file layer can catch a bad manual edit; correctness is guaranteed only by going through the CLI, so a hand edit silently breaks the brain's invariants.
The exact command surface (update-root / create-page / update-truth / reindex / ls …) and the page-category taxonomy live in the brain-page skill — read it before creating or modifying any page. Resolve <brain-page-bundle> to wherever that skill is installed (in the brain.md source repo, skills/brain-page/); define the shell function brain() { node <brain-page-bundle>/bin/brain.mjs "$@"; } (a function is portable across bash and zsh, unlike BRAIN="node …"; $BRAIN …, which only word-splits in bash) and run everything from the project root.
Step 0 — Pick the mode
Inspect the project to decide which path you are on:
- Brownfield — there is substantial source code, and/or real
git loghistory. There is something to read; go to Brownfield. - Greenfield — a near-empty repo: no meaningful source, little or no history. There is nothing to read; go to Greenfield.
When it is genuinely mixed (a little code, a little history), prefer Brownfield for whatever can be inferred, and fall back to interview questions for the parts the code can't tell you.
Brownfield — synthesize from code, docs, and history
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.
- 1mo ago First seen · 96 lines · 74 tokens per session scan A d69a92c85499
brain-bootstrap is a skill published in the GitHub repository mindmuxai/brain.md (576 stars, last pushed yesterday), licensed Apache-2.0. It adds 74 tokens to every session and 1,674 once invoked, about $0.0003 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 skills, from other repositories
chain
Inject the 3 most recent session IDs for the current workspace into the prompt before Claude responds. Use when starting work and wanting recent session context.
recall
Retrieve what LemonCrow already learned from your past sessions — semantic recall over indexed sessions, durable facts, and extracted lessons. Use for 'have we seen this before', 'what did we learn about X', 'what does LemonCrow remember', or /recall. Read-only; importing, indexing, and extraction run in the LemonCrow…
using-memory
Persistent dual-layer memory engine with Notebook facts, curated RAG knowledge base, agent-driven knowledge graph, and general MCP helpers. Trigger proactively whenever user preferences, project conventions, technology stack choices, or architecture decisions are introduced, or when querying ingested documentation…
agent-context-crystallizer
Preserve high-signal work context with local checkpoints and session crystals using the agent-crystallize CLI. Use before compaction, handoff, session end, cross-agent transfer, after major decisions/findings/failures, or when the user asks to checkpoint, crystallize, preserve context, save open loops, or create a…
mnemon
Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.
mnemon
Persistent graph-based memory. Recall context before responding, remember insights after. Each group has private memory; global memory is read-only.