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-setupgit 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-setup)<a href="https://agentmods.dev/skills/mindmuxai/brain.md/brain-setup"><img src="https://agentmods.dev/badge/skills/mindmuxai/brain.md/brain-setup/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-setup"><img src="https://agentmods.dev/badge/skills/mindmuxai/brain.md/brain-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Agent Snooping · line 91 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
- medium Rogue Agent · line 16 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00063 | $0.02490 |
| Opus 5.5 | $0.00025 | $0.00996 |
| Sonnet 5.5 | $0.00013 | $0.00498 |
| Haiku 4.5 | $0.00006 | $0.00249 |
Grade A, and why
brain-setup 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
brain-setup
This skill bootstraps a project into the Open Project Brain Standard: it drops in the protocol entry point and the brain/ skeleton so the brain-page and brain-ingest skills (and the brain CLI) have something to work with. It is idempotent — safe to run again on an already-initialized project.
Preferred one-shot path: from the project root run:
node <brain-page-bundle>/bin/brain.mjs init
That command ensures BRAIN.md, scaffolds empty brain data (brainRoot-aware), and default-wires CLAUDE.md + AGENTS.md (create if missing; if present, only update/append the marked brain block — never whole-file overwrite). Use the steps below when you need the optional pre-commit hook, the optional Claude Code or Codex SessionStart hook, or are explaining the flow.
NEVER hand-edit any file under the brain directory. All reads and writes MUST go through the
brainCLI. Manual edits are unsupported and illegitimate. This scaffold creates the brain once; from then on every read and write is abrainsubcommand. There is no validator and nothing at the file layer can catch a bad manual edit, so a hand edit silently breaks the brain's invariants.
Run this from the target project's root. The skill bundle ships the templates under assets/ and the hook under hooks/; resolve <this-skill-bundle> to the directory this SKILL.md lives in.
Core invariant: there is exactly one brain, at the resolved location. The brain's data directory is location-independent — it lives at
./brainby default, but a MindMux-managed project redirects it viabrainRootin./.mindmux/preferences.json(often an absolute path to an external sidecar directory). This skill MUST resolve that location before scaffolding, and MUST NOT create a second, local./brainwhen abrainRootis set — doing so produces a split brain (an empty local skeleton shadowing the real external brain). TheBRAIN.mdprotocol document is separate: it always lives in the project root regardless of where the brain data lives.
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/BRAIN.md 18 KB
- assets/brain/architecture.md 455 B
- assets/brain/background.md 409 B
- assets/brain/flow.md 462 B
- assets/brain/index.md 89 B
- assets/brain/mindmap.md 294 B
- assets/brain/pages/.gitkeep 0 B
- assets/brain/roadmap.md 333 B
- assets/brain/stack.md 425 B
- hooks/pre-commit 1.5 KB
- hooks/session-start 2.0 KB
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 Changed · +22 lines · +3 tokens per session scan B → A 1b3fa805a163
- 1mo ago First seen · 110 lines · 60 tokens per session scan B a6ae879c8e00
brain-setup is a skill published in the GitHub repository mindmuxai/brain.md (574 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 63 tokens to every session and 2,490 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.
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…
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…
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…
deja-search
Search deja before re-deriving past work: when the user refers to earlier sessions or decisions, before debugging an error, and before implementing something that may already exist. It searches this machine's own history across every AI coding tool used on it, going back further than deja itself was installed.
mnemon
Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.