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 agentmods add skills/josherau/claude-operating-core/second-brainnpx skills add josherau/claude-operating-core --skill second-braingit clone --depth 1 https://github.com/josherau/claude-operating-coreWrote 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/josherau/claude-operating-core/second-brain)<a href="https://agentmods.dev/skills/josherau/claude-operating-core/second-brain"><img src="https://agentmods.dev/badge/skills/josherau/claude-operating-core/second-brain.svg" alt="Measured on agentmods" 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 | $0.00104 | $0.01619 |
| Opus 5 | $0.00052 | $0.00809 |
| Sonnet 5 | $0.00021 | $0.00324 |
| Haiku 4.5 | $0.00010 | $0.00162 |
Grade A, and why
second-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 4d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Second Brain — the vault every session reads and feeds
A session's context dies when the session ends. A vault of plain markdown files does not. This skill sets up and operates that vault: one folder tree that holds the registry of everything you work on, the conventions for writing it down, and the accumulated lessons that make every future session smarter than the last one.
The machinery is three habits enforced by files:
- Boot from the brain. Every session starts by reading the vault's own CLAUDE.md — the registry, the rules, the pointers to deeper indexes.
- Write back before ending. Substantive sessions end with a session log, updated notes, and new learnings. No mental notes; files or it didn't happen.
- Garden continuously. A recurring pass (see the
vault-gardenerskill) removes entropy so recall stays precise as the vault grows.
Mode 1: SETUP — bootstrap a new vault
Trigger: "second-brain setup" or any request to create a knowledge vault. Ask only for two things if not evident: where the vault should live ({VAULT}, e.g. ~/Documents/brain — pick a synced folder if the user works across machines) and the user's main work contexts (businesses, clients, or domains — these become the registry rows and #ctx/* tags).
- Create the structure:
{VAULT}/
├── Projects/ One folder per active project; each gets a Title Case index note
├── Areas/ Ongoing responsibilities with no end date
├── Resources/ Reference material, guides, imported docs
├── Inbox/ Quick capture; the gardener files it later
├── Session-Logs/ One subfolder per project slug
├── Archive/ Completed/inactive items from anywhere above
├── Templates/ Note templates
└── System/
├── learnings/ One lesson per file (see extract-approach)
├── standards/ Pass/fail quality bars per deliverable type
└── dashboards/ Optional overview notes
Projects/Areas/Resources/Archive is Tiago Forte's PARA method; Session-Logs and System are our additions — the session memory and the self-improvement machinery respectively.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 82 lines · 104 tokens per session scan A b2ea6bd28610
second-brain is a skill published in the GitHub repository josherau/claude-operating-core (3 stars, last pushed 24d ago), licensed MIT. It adds 104 tokens to every session and 1,619 once invoked, about $0.0005 per session on Opus 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-31.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
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…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…