By sonthanh
Transform Obsidian into an autonomous second brain that extracts book insights, captures session decisions, audits principles, processes email, implements GitHub issues with TDD, and runs nightly vault maintenance.
Audit a target artifact through P1 (First Principles / Simple scales) ONLY. Member of an `audit-*` team launched by `/audit --team`. Read-only on project files; writes a single per-teammate JSON.
Audit a target artifact through P2 (Start with Why) ONLY. Member of an `audit-*` team launched by `/audit --team`. Read-only on project files; writes a single per-teammate JSON.
Audit a target artifact through P3 (Hormozi Lens) ONLY. Member of an `audit-*` team launched by `/audit --team`. Read-only on project files; writes a single per-teammate JSON.
Audit a target artifact through P4 (Concrete drives abstract) ONLY. Member of an `audit-*` team launched by `/audit --team`. Read-only on project files; writes a single per-teammate JSON.
Audit a target artifact through P5 (Manage causes, not effects) ONLY. Member of an `audit-*` team launched by `/audit --team`. Read-only on project files; writes a single per-teammate JSON.
Use when extracting deep insights from a book and connecting them to vault zones (business, personal, thinking)
Turn a goal, task, or existing issue into autonomous work — grill when fuzzy, file/relabel AFK issues, health-check the loop spine, hand off to the schedulers. Triggers: '/afk <goal|task|N>', 'make this AFK', 'finish this while I'm away'. Execute NOW instead → /impl N or cox N.
Capture key moments mid-session with full context. Triggers on natural language: aha, mark this, key moment, that's interesting, remember this decision, this is important, breakthrough
Extract knowledge từ Airtable bases vào vault dưới dạng linked entity pages. Sonnet worker + Opus reviewer ≥95% gate, mandatory HITL re-anchor mỗi base mới. Use khi seeding historical knowledge từ company Airtable bases.
One-shot principle check via advisor. Use when you want to stress-test a decision, plan, or code against your principles — non-interactive, returns findings. For interactive stress-testing, use /grill instead.
Matches all tools
Hooks run on every tool call, not just specific ones
Executes bash commands
Hook triggers when Bash tool is used
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Modifies files
Hook triggers on file write and edit operations
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Uses power tools
Uses Bash, Write, or Edit tools
Your AI tools give generic answers because they don't know how you think. Brain OS fixes that — it's a Claude Code plugin that turns your Obsidian vault into a second brain that learns, thinks, and acts with you.
One line. Plugin + vault + everything ready in under 2 minutes:
curl -sSL https://raw.githubusercontent.com/sonthanh/brain-os-plugin/main/install.sh | bash
Already have an Obsidian vault? Point to it:
curl -sSL .../install.sh | bash -s -- --vault ~/my-vault
Just want the plugin (no vault setup):
curl -sSL .../install.sh | bash -s -- --plugin-only
After install, try your first command:
/think What should I focus on this week?
Brain OS reads your context, goals, and recent activity — then thinks with you. Not generic advice. Your priorities, your situation.
Power feature:
/studyreads an entire book, extracts atomic notes, validates each one against NotebookLM (159/159 checks, avg 97/100 accuracy), and connects insights to your vault — fully autonomous.
See Getting Started for the full setup walkthrough and first use cases.
Tasks (/pickup, /handover, /status, /impl, /slice) live as GitHub issues in a repo you own — not in Markdown files. This solves multi-session concurrency (atomic state, stable IDs, no merge conflicts).
One-time setup:
your-username/my-tasks.gh auth login if not already authenticated.gh_task_repo: in ~/.brain-os/brain-os.config.md:
gh_task_repo: your-username/my-tasks
R=your-username/my-tasks
gh label create status:ready --color 0E8A16 -R $R
gh label create status:in-progress --color 1D76DB -R $R
gh label create status:blocked --color B60205 -R $R
gh label create status:backlog --color C5DEF5 -R $R
gh label create priority:p1 --color D93F0B -R $R
gh label create priority:p2 --color FBCA04 -R $R
gh label create priority:p3 --color FEF2C0 -R $R
gh label create priority:p4 --color E1E4E8 -R $R
gh label create weight:heavy --color 5319E7 -R $R
gh label create weight:quick --color 006B75 -R $R
gh label create owner:human --color F9D0C4 -R $R
gh label create owner:bot --color BFDADC -R $R
gh label create type:handover --color FF6B6B -R $R
gh label create type:plan --color 8A2BE2 -R $R
Without gh_task_repo configured, skills silently skip the task panel and work in read-only vault mode.
Claude Code skills solve specific tasks. But context is scattered across projects, skills, and agents. Each one knows a piece — none sees the full picture. Decisions from fragmented context are generic: "correct but not yours."
Think of it like onboarding a team lead. You don't start by delegating decisions — you teach them how you think first. Give them the books you've read, the frameworks you use, the goals you're chasing. Then gradually let them act.
That's what Brain OS does with AI. One vault, one knowledge layer. Every skill reads from the same source of truth — your context, your knowledge, your decisions. The more you use it, the more it thinks like you.
Karpathy is building something similar with "LLM Knowledge Bases." Same direction, different purpose — he builds a wiki to read. Brain OS is an OS to act.
Read the full story: Day 1 — I Taught an AI to Read a Book
| Skill | When to use |
|---|---|
/study | When you want to master a book end-to-end: extract, validate, absorb into your vault |
/self-learn | When you want to extract and validate knowledge from a book (the core of /study) |
/research | When you need to understand a topic — searches the web and synthesizes a cited report |
| Skill | When to use |
|---|---|
/think | When you're stuck on a decision, exploring an idea, or want deep reflection on anything |
/grill | When you need a plan stress-tested until it's bulletproof |
/audit | One-shot principle check via advisor — non-interactive, returns findings |
npx claudepluginhub sonthanh/brain-os-pluginPersistent Obsidian-based memory for coding agents. Automatically orients from a knowledge vault at session start, navigates project architecture via graph traversal, and writes discoveries back to the vault.
Bidirectional knowledge flow between Claude Code and Obsidian — 20 MCP tools, skills, and hooks for PKM
Create and edit Obsidian vault files including Markdown, Bases, and Canvas. Use when working with .md, .base, or .canvas files in an Obsidian vault.
Second Brain automation for Obsidian vaults — entity management, ingestion, compression, and sync via Claude Code skills
AI thinking partner for your Obsidian vault — process, recall, synthesize, research with evidence-backed learning science
A self-developing knowledge management system for Claude Code. Bridges AI memory to an Obsidian vault with feature-organized spine notes, auto-capture skills, and color-coded graph visualization.