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 Abilityai/abilities --skill setup-braingit clone --depth 1 https://github.com/Abilityai/abilitiesWrote 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/abilityai/abilities/setup-brain)<a href="https://agentmods.dev/skills/abilityai/abilities/setup-brain"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/setup-brain/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/abilityai/abilities/setup-brain"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/setup-brain.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.00016 | $0.00726 |
| Opus 5.5 | $0.00006 | $0.00290 |
| Sonnet 5.5 | $0.00003 | $0.00145 |
| Haiku 4.5 | $0.00002 | $0.00073 |
Grade A, and why
setup-brain 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Brain Vault
Initialize a Zettelkasten-style knowledge management system.
Step 1: Ask Configuration
Use AskUserQuestion:
Question 1: "Where should the Brain vault be created?"
- Options:
- "Brain/ folder (Recommended)" - Standard location
- "Custom location" - Specify a different path
Question 2: "What type of knowledge will you primarily store?"
- Options:
- "General knowledge & insights" - Broad topics
- "Technical/coding notes" - Development focused
- "Research & learning" - Academic style
- "Mixed/All types"
Step 2: Create Directory Structure
Create the Brain vault structure:
mkdir -p Brain/00-Inbox/Quick\ Captures
mkdir -p Brain/00-Inbox/Raw\ Materials
mkdir -p Brain/01-Sources/Books
mkdir -p Brain/02-Permanent
mkdir -p Brain/03-MOCs
mkdir -p Brain/04-Output/Articles
mkdir -p Brain/04-Output/Draft\ Posts
mkdir -p Brain/04-Output/Projects
mkdir -p Brain/05-Meta/Changelogs
mkdir -p Brain/05-Meta/Templates
mkdir -p Brain/Document\ Insights
Step 3: Create Essential Files
Brain/CHANGELOG.md:
# Brain Changelog
## [Session Date]
- Brain vault initialized
- Structure created with standard directories
Brain/04-Output/Articles/ARTICLE-INDEX.md:
# Article Index
Central registry of all articles in the vault.
| Title | Created | Status | Topics |
|-------|---------|--------|--------|
| (none yet) | - | - | - |
Brain/05-Meta/Templates/permanent-note.md:
---
created: YYYY-MM-DD
updated: YYYY-MM-DD
created_by: [agent-name]
updated_by: [agent-name]
tags: []
---
# Note Title
[Content goes here]
## Connections
- [[Related Note 1]]
- [[Related Note 2]]
Step 4: Update CLAUDE.md
Add brain configuration to CLAUDE.md:
## Brain Vault
Knowledge management using Zettelkasten method.
### Structure
- `Brain/00-Inbox/` - New captures, raw ideas
- `Brain/02-Permanent/` - Atomic, interconnected notes
- `Brain/03-MOCs/` - Maps of Content (indexes)
- `Brain/04-Output/` - Generated content
- `Brain/05-Meta/` - Changelogs and templates
### Note Format
All notes MUST have YAML frontmatter:
- created, updated (dates)
- created_by, updated_by (agent attribution)
- tags (array)
### Commands
- `/create-note` - Create a new permanent note
- `/search-brain` - Search the vault
- `/find-connections` - Discover note relationships
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 · 122 lines · 16 tokens per session scan A 5c4d69640ac0
setup-brain is a skill published in the GitHub repository Abilityai/abilities (12 stars, last pushed 3d ago), licensed MIT. It adds 16 tokens to every session and 726 once invoked, about $0.0001 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
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
Migrate
Intakes external content, classifies chunks against LifeOS taxonomy, commits with provenance. Sources: .md/.txt, stdin, LifeOS dirs, CLAUDE.md/Cursor/OpenAI Custom Instructions, Obsidian/Notion/Apple Notes exports. MigrateScan classifies → routing table. MigrateApprove with…
wiki-dashboard
Create dynamic, queryable Obsidian dashboard views using Bases or Dataview. Use for auto-updating tables, indexes, or structured views of vault content; not for ordinary question answering.
session-compact
AI DevKit · Compact a historical AI coding session with Jev when context is long, work is handed off or resumed, or durable continuation facts and memory candidates need extraction.
relevance-coarse-filter
Cheap, high-recall first-pass filter that removes obvious junk from a detector candidate pool before expensive story-origin research and PR judgment. Decides keep, monitoronly, or reject — never ranks, writes angles, verifies dates, or decides whether to pitch.
daily-briefing
Proactive daily briefing that fires on a recurring schedule, pulls recent memory and workspace context, composes a structured summary (action items, progress, radar, next steps), and delivers it to all active channels. Enable with a time like "set up my daily briefing at 9am". Disable, reschedule, or check status at…