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 SanderMoon/local-brain --skill brain-setupgit clone --depth 1 https://github.com/SanderMoon/local-brainWrote 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/sandermoon/local-brain/brain-setup)<a href="https://agentmods.dev/skills/sandermoon/local-brain/brain-setup"><img src="https://agentmods.dev/badge/skills/sandermoon/local-brain/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/sandermoon/local-brain/brain-setup"><img src="https://agentmods.dev/badge/skills/sandermoon/local-brain/brain-setup.svg" alt="Reviewed on agentmods" width="80" 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.00049 | $0.00900 |
| Opus 5.5 | $0.00020 | $0.00360 |
| Sonnet 5.5 | $0.00010 | $0.00180 |
| Haiku 4.5 | $0.00005 | $0.00090 |
Grade B, and why
brain-setup scanned grade B with 1 finding 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
Briefly explain what Local Brain does in one or two sentences. Do not lecture. Then ask: How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
brain-setup: First-Time Setup Wizard
Guide the user through setting up their Local Brain workspace conversationally. This should feel like talking to a new executive assistant on their first day — curious, helpful, and efficient.
Trigger Phrases
- "Set up my brain", "Get started", "I'm new here"
- "Help me organize my projects"
- "I just installed brain"
- First interaction when the brain is empty
Pre-flight Check
Call get_brain_overview to assess the current state:
- If no brain exists or brain is completely empty (no projects, no dump items): run the full setup
- If projects already exist: offer to add more projects or refine existing ones — do not re-run full setup
- If only dump items exist: offer to organize them into projects as part of setup
Workflow
Step 1 — Welcome and Context
Briefly explain what Local Brain does in one or two sentences. Do not lecture. Then ask:
"What are you working on right now? Tell me about your projects — they can be work tasks, side projects, personal goals, anything."
Let the user talk naturally. Extract project names, descriptions, and any mentioned tasks or deadlines from their response.
Step 2 — Create Projects
For each project identified:
- Suggest a short, kebab-case name (e.g., "website-redesign", "q1-planning")
- Confirm the name and description with the user
- Call
create_projectfor each
Do not create more than 3-5 projects in the first pass. If the user mentions more, note them and say: "Let's start with these — you can always add more later."
Step 3 — Populate Initial Tasks
For each project, ask:
"What needs to happen next for [project]? Any deadlines?"
Convert responses into concrete tasks with:
- Clear, actionable descriptions (imperative form: "Ship v2", not "v2 shipping")
- Due dates when mentioned ("by Friday" → the actual date)
- Priority 1 for anything the user emphasizes as urgent or important
Call create_todo_in_project in batches per project.
Step 4 — Handle "I Don't Know"
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 · 98 lines · 49 tokens per session scan B e1831415891d
brain-setup is a skill published in the GitHub repository SanderMoon/local-brain (9 stars, last pushed 7mo ago), licensed MIT. It adds 49 tokens to every session and 900 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
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.
mnemon
Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.
mnemon
Persistent memory for MiniMax Code. Recall durable context, store important facts and decisions, and link related memories with the mnemon CLI.
mnemon
Persistent memory CLI for CodeBuddy. Store facts, recall past knowledge, link related memories, manage lifecycle.