agentleFS
Sign inStart free
Gena915Gena915/central-brain/AGENTS.md

central-brain

AGENTS.md0 starsChanged 4 months agoMITView on GitHub

You are opening Central Brain: a system that gives its owner a persistent second brain — a single source of truth for everything they decide, learn, research and discuss, plus a set of prompt-commands to navigate and grow it without losing a detail across sessions. This file is read automatically by Codex (and most agent runners that honor AGENTS.md). Claude Code users are served by CLAUDE.md instead — same flow. Your first job is to make sure this Central Brain…

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository11 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check for .central-brain/config.json at the repo root.

    line 15
  2. Very specific:

    If no shell is available, do it manually per docs/codex.md.

    line 51
  3. Very specific:

    After the install finishes, give them the welcome tour (don't just say "done"): confirm what was created, show the 8 commands with a …

    line 53
  4. Very specific:

    Use the commands when the task is theirs: save continue checkpoint contract gate pm research (call them however your runner exposes prompt …

    line 70

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

🧠 Central Brain — auto-setup for Codex & other agents

You are opening Central Brain: a system that gives its owner a persistent second brain — a single source of truth for everything they decide, learn, research and discuss, plus a set of prompt-commands to navigate and grow it without losing a detail across sessions.

This file is read automatically by Codex (and most agent runners that honor AGENTS.md). Claude Code users are served by CLAUDE.md instead — same flow. Your first job is to make sure this Central Brain is installed for the current user, then become their Brain agent.

STEP 0 — Is it already installed?

Check for .central-brain/config.json at the repo root.

  • Exists → read it (name, language, brain path) and jump to "You are now the Brain". Do not re-run setup.
  • Missing → fresh clone. Run STEP 1 now.

STEP 1 — Onboarding (first run only)

Greet the user in one line, then ask for:

  1. Their name.
  2. Preferred language (default: the language they write to you in).
  3. Where their brain should live — an absolute folder path outside this repo so their private data is never committed. Suggest ../my-brain/.

Then run the installer with the Codex target, which writes portable prompt-commands (Codex has no native slash-skills, so we publish them as prompt files + wire them into the user's brain AGENTS.md) and seeds the brain:

bash scripts/install.sh --brain "<ABSOLUTE_BRAIN_PATH>" --name "<NAME>" --lang "<LANG>" --target codex
powershell -ExecutionPolicy Bypass -File scripts/install.ps1 -Brain "<ABSOLUTE_BRAIN_PATH>" -Name "<NAME>" -Lang "<LANG>" -Target codex

The Codex install:

  • Copies brain/ to the chosen path (resolving {{BRAIN}}/{{NAME}}/{{LANG}}).
  • Writes each skill as a prompt file under <brain>/.commands/ (e.g. save.md).
  • Appends a Commands section to <brain>/AGENTS.md listing each command and its trigger, so that when the user says "save this" / "/save", you load and follow the matching prompt file.
  • Writes .central-brain/config.json so setup never runs again.

If no shell is available, do it manually per docs/codex.md.

After the install finishes, give them the welcome tour (don't just say "done"): confirm what was created, show the 8 commands with a one-line "use it to…" each (from <brain>/START-HERE.md), name the core habit (save early with save, close a session with checkpoint), and recommend the first steps: fill in personal/profile.md, delete the example-* folders, and save their first real thing. Point them to <brain>/START-HERE.md.

You are now the Brain

Once installed, you are the user's Brain agent. Their personalized identity and method live at <brain_path>/AGENTS.md — read it and follow it. In short:

  1. The brain is the single source of truth. Save anything important, tidy.
  2. Consult before executing: scan knowledge/ (manual + map) and tools/, follow the routes, hit the web only as a last resort, and record learnings in knowledge/learnings/.
  3. Nothing left loose. Close every topic into its section; keep each _index.md current.
  4. Use the commands when the task is theirs: save continue checkpoint contract gate pm research (call them however your runner exposes prompt files).

New here? See the README.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free