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-ingestgit 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-ingest)<a href="https://agentmods.dev/skills/mindmuxai/brain.md/brain-ingest"><img src="https://agentmods.dev/badge/skills/mindmuxai/brain.md/brain-ingest.svg" alt="Measured on agentmods" 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.00048 | $0.00936 |
| Opus 5 | $0.00024 | $0.00468 |
| Sonnet 5 | $0.00010 | $0.00187 |
| Haiku 4.5 | $0.00005 | $0.00094 |
Grade A, and why
brain-ingest 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 7d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
brain-ingest
This skill is about "turning scattered input into structured brain knowledge". The input can be a conclusion from a conversation, an external document, a piece of research, or the decisions behind a set of code changes. The goal is to land that knowledge in the right place, the right category, and the right structure — and to write it through the brain CLI so it is correct by construction.
Reach for this process not only when explicitly asked to "ingest" something. The brain is the project's persistent memory (see BRAIN.md), so trigger it proactively whenever knowledge crystallizes — a decision settled in discussion, a requirement or constraint agreed, an insight that will still matter in six months. Capture it as it surfaces rather than waiting to be told.
Every read and write below is a brain CLI subcommand (list-pages / read-page / read-root to read; create-page / update-truth / … to write). The command details and the category taxonomy live in the brain-page skill — read it before creating or modifying any page.
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.
Process
1. Break down the input
Split the input into individual atomic knowledge points. A knowledge point = one judgment / fact / decision that stands on its own. Ignore purely procedural chatter.
2. Place each knowledge point (see "Choosing where to write" in BRAIN.md)
- Changes the project's overall positioning / architecture / stack / roadmap → rewrite the corresponding root page with
brain update-root <slug>(background/architecture/flow/mindmap/stack/roadmap). - About a specific entity (a decision / concept / person / reference / sub-project) → create or update a page.
- It's common for one knowledge point to touch both — write to both sides.
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.
- 7d ago First seen · 57 lines · 48 tokens per session scan A 69efa874dc22
brain-ingest is a skill published in the GitHub repository mindmuxai/brain.md (531 stars, last pushed 16d ago), licensed Apache-2.0. It adds 48 tokens to every session and 936 once invoked, about $0.0002 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 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…
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.
mnemon
Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.