Agent skill

Brain Ingest

by mindmuxai in mindmuxai/brain.md

The process for digesting a conversation, document, or research result, classifying it, and writing it down as brain content (a root-page update or a new/updated page) through the brain CLI.

Apache-2.0Auto-check passedAgent Workflows

Install Brain Ingest

skills CLI
$ npx skills add mindmuxai/brain.md --skill brain-ingest -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mindmuxai/brain.md brain-ingest --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mindmuxai/brain.md.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/brain-ingest .claude/skills/brain-ingest && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
brain-ingest
GitHub stars
566
Token cost
~1k tokens
SKILL.md length
566 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
Apache-2.0

At a glance

The process for digesting a conversation, document, or research result, classifying it, and writing it down as brain content (a root-page update or a new/updated page) through the brain CLI.

  • Works in 5 steps: Break down the input → Place each knowledge point (see… → Decide between "create" and "update… → …
  • Tasks that involve Agent memory
  • SKILL.md covers Process and Principles
  • Calls node

What it does

Brain Ingest is an agent skill from mindmuxai/brain.md. The process for digesting a conversation, document, or research result, classifying it, and writing it down as brain content (a root-page update or a new/updated page) through the brain CLI.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Agent memory. The repository describes itself as: A persistent, file-based memory layer for coding agents — give Claude Code, Codex & others a project brain (durable decisions, requirements, constraints) via a zero-dependency CLI. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Agent memory

Example prompts

  • “/brain-ingest”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Break down the input
  2. Place each knowledge point (see "Choosing where to write" in BRAIN.md)
  3. Decide between "create" and "update existing"
  4. Write
  5. Verify

What it can do on your machine

Read from SKILL.md and the folder at commit 8064f33. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Brain Ingest loads about 1k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 566 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~51
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mindmuxai/brain.md at commit 8064f33, republished under its Apache-2.0 licence (© mindmuxai). 566 words, ~1,046 tokens.

Download SKILL.mdSave it as .claude/skills/brain-ingest/SKILL.md (or your agent's skills folder).
name
brain-ingest
description
The process for digesting a conversation, document, or research result, classifying it, and writing it down as brain content (a root-page update or a new/updated page) through the `brain` CLI.

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 brain CLI. 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.
Show full SKILL.md (249 more words)Show less
3. Decide between "create" and "update existing"
  • First run brain list-pages (and brain read-page <id> on likely hits) to look for an existing page on the same topic.
  • Found → update it: brain update-truth --id <id> (rewrites compiled_truth and appends a timeline entry atomically), or brain append-timeline for a new piece of evidence that doesn't change the conclusion.
  • Not found → create it: read the brain-page skill, then brain create-page, then fill in the real understanding with brain update-truth.
  • Avoid duplication: don't scatter one topic across multiple pages.
4. Write
  • All writes go through the brain CLI — see brain-page for exact commands. Never hand-edit frontmatter or timelines.
  • Root pages are rewritten wholesale via update-root; they have no timeline.
  • Write the body in the user's working language; keep technical identifiers (ids, slugs, field names, paths) verbatim.
  • Connect related pages explicitly with [[page-id]].
5. Verify

The write commands reindex for you, and correctness is guaranteed by construction — there is no validator to run. To optionally confirm that every [[page-id]] resolves:

node <brain-page-bundle>/bin/brain.mjs lint-links

The CLI makes "compiled_truth changed but the timeline entry was forgotten" structurally impossible; the only way to break it is a hand edit, which is why you must never make one.

Principles

  • Prefer less but accurate. Only capture knowledge that still matters in six months and is hard to reconstruct from the code / git.
  • Every compiled_truth rewrite carries its own timeline trace — update-truth guarantees this, keeping the chain of evidence unbroken.
  • Keep the category boundaries clear — the taxonomy lives in the brain-page skill.

© mindmuxai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/brain-ingest of mindmuxai/brain.md.

Open the folder on GitHubat commit 8064f33

Compare with similar skills

Brain Ingest next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Brain Ingest compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Brain Ingest this skillmindmuxai/brain.md566—~1kAutomated safety check: PassApache-2.0
Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills21k—~1.9kAutomated safety check: PassMIT
Beads Task Memorygastownhall/beads28k—~1.2kAutomated safety check: PassMIT
Reflect on Session Learningscursor/plugins11k5 repos~1.2kAutomated safety check: PassNone
MemPalace Memory SearchMemPalace/mempalace59k—~1.4kAutomated safety check: PassMIT
Compound Learning WriterEveryInc/compound-engineering-plugin25k—~2kAutomated safety check: PassMIT

Similar skills

  • Neat-Freak Knowledge Closeout

    KKKKhazix/khazix-skills

    Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.

    21k GitHub stars~1.9k tokensUpdated 8 days ago
    Agent WorkflowsAuto-check passed
  • Beads Task Memory

    gastownhall/beads

    Tracks multi-session work with dependencies in the bd issue tracker so the agent can find ready tasks and recover its context after conversation compaction.

    28k GitHub stars~1.2k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Official

    Starts three parallel reviewer subagents over the current conversation transcript, then turns their findings into concrete edits to existing skills.

    11k GitHub starsUsed in 5 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • MemPalace Memory Search

    MemPalace/mempalace

    Mines project files and conversation exports into a local, searchable memory palace and recalls past work by semantic search through the mempalace CLI.

    59k GitHub stars~1.4k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Compound Learning Writer

    EveryInc/compound-engineering-plugin

    Records one solved and verified problem as a durable learning in the repository, but only when the reasoning is not already clear from the final code, tests or docs.

    25k GitHub stars~2k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed
  • Searches past Claude Code, Codex and Cursor sessions and summarizes what was worked on, tried or decided, using extraction scripts instead of reading raw logs.

    24k GitHub stars~3.1k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from mindmuxai/brain.md

  • Brain Setup

    mindmuxai/brain.md

    Bootstrap the Open Project Brain Standard into the current project — prefer brain init (ensure BRAIN.md, scaffold empty brain brainRoot-aware, default-wire CLAUDE.md + AGENTS.md).

    566 GitHub stars~2.7k tokensUpdated 28 days ago
    Auto-check passed
  • Brain Bootstrap

    mindmuxai/brain.md

    Seed a freshly-scaffolded brain with real project knowledge — on an existing (brownfield) project read the code, docs, and git log to draft the six root pages and capture key historical decisions…

    566 GitHub stars~1.8k tokensUpdated 28 days ago
    Auto-check passed
  • Brain Page

    mindmuxai/brain.md

    Operating manual for reading and writing a project's brain — every read and write goes through the bundled zero-dependency brain CLI; never hand-edit brain files.

    566 GitHub stars~2.5k tokensUpdated 28 days ago
    Auto-check passed

Categories

Questions about Brain Ingest

What does Brain Ingest do?

The process for digesting a conversation, document, or research result, classifying it, and writing it down as brain content (a root-page update or a new/updated page) through the brain CLI. md. The process for digesting a conversation, document, or research result, classifying it, and writing it down as brain content (a root-page update or a new/updated page) through the brain CLI.

When should I use Brain Ingest?

Brain Ingest fits situations like: tasks that involve Agent memory.

How do I install Brain Ingest in Claude Code?

Run `npx skills add mindmuxai/brain.md --skill brain-ingest -a claude-code`. Or copy the skill folder (skills/brain-ingest in mindmuxai/brain.md) into .claude/skills/brain-ingest in your project. Claude Code loads it when a task matches its description.

How do I install Brain Ingest in Codex?

Run `npx skills add mindmuxai/brain.md --skill brain-ingest -a codex`. Or copy the skill folder (skills/brain-ingest in mindmuxai/brain.md) into .agents/skills/brain-ingest in your project. Codex loads it when a task matches its description.

Can I use Brain Ingest in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mindmuxai/brain.md --skill brain-ingest -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/brain-ingest, .gemini/skills/brain-ingest, .github/skills/brain-ingest and .opencode/skills/brain-ingest in your project.

What does Brain Ingest need to run?

Going by SKILL.md and its folder, Brain Ingest needs the command-line tools its instructions call (node).

Does Brain Ingest access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Brain Ingest safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Brain Ingest use?

Brain Ingest is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Brain Ingest use?

About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Brain Ingest?

Skills that share tags, products or a category with Brain Ingest: Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars), Beads Task Memory (gastownhall/beads, 28k stars), Reflect on Session Learnings (cursor/plugins, 11k stars) and MemPalace Memory Search (MemPalace/mempalace, 59k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Brain Ingest?

mindmuxai (a GitHub organization) maintains it in mindmuxai/brain.md, which has 566 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on September 11, 2026.

Source: mindmuxai/brain.md on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.