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/jzhao234/big-brain/capturenpx skills add jzhao234/big-brain --skill capturegit clone --depth 1 https://github.com/jzhao234/big-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/jzhao234/big-brain/capture)<a href="https://agentmods.dev/skills/jzhao234/big-brain/capture"><img src="https://agentmods.dev/badge/skills/jzhao234/big-brain/capture.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.1 | $0.00070 | $0.00307 |
| Opus 5 | $0.00035 | $0.00153 |
| Sonnet 5 | $0.00014 | $0.00061 |
| Haiku 4.5 | $0.00007 | $0.00031 |
Grade A, and why
capture 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 5d 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.
What it actually says
capture
Get it into the vault before it's lost. Don't organize, don't ask clarifying questions — that's what triage is for. The target vault is whatever big-brain resolves (BIG_BRAIN_VAULT env, --vault, or nearest brain.config.json); don't hardcode a path.
- If there's an argument, capture it verbatim (lightly cleaned):
big-brain capture "<text>". If the note obviously belongs to an active project instead (it names one), append it to that project's## Notesand say so. - If there's no argument, capture the most recent noteworthy thing from the conversation (the idea/decision/fact just discussed) — state in one line what you captured.
- If the capture contains something actionable ("need to", "don't forget to"), also offer: "want this as a task on ?"
Confirm with one line: where it went. Nothing else. (If the vault has git auto-commit on, the capture is committed automatically.)
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.
- 5d ago First seen · 20 lines · 70 tokens per session scan A e21a003360f7
capture is a skill published in the GitHub repository jzhao234/big-brain (0 stars, last pushed 4d ago), licensed MIT. It adds 70 tokens to every session and 307 once invoked, about $0.0003 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
lint-brain
Run health checks over the brain vault - find orphan notes, broken wikilinks, missing frontmatter, stale projects, and missing cross-links. Use when asked to "lint the brain", "health check", "vault hygiene", or "/lint-brain".
ingest-article
Ingest an article from a URL or raw text into the brain vault. Extracts key knowledge, determines placement, creates or updates notes, and links to relevant projects. Use when the user shares a URL or text and wants to absorb it into their knowledge base.
wrap-session-up
End-of-session review for a Claude Code conversation. Replays what was discussed, checks for open action items, documents relevant outcomes in the brain vault, and creates Todoist tasks for anything untracked. Use at the end of a work session to ensure nothing falls through the cracks.
kickoff
Guided first-run setup for a forked brain-starter vault. Walks through identity, first project, semantic search, integrations, indexes, and the first commit - verifying each phase before moving on. Use when the user has just forked or cloned brain-starter, says "set up my brain", "I just forked brain-starter", or runs…
project-sync
On-demand AI-powered sync of a project's repo state into the brain vault. Reads live git/GitHub/Jira data, updates the project status doc, and makes targeted edits to relevant brain docs where content is clearly stale. Triggered by "/project-sync [name]", "sync [project]", "what's the current state of [project]".
save-answer
File a conversation output (research, analysis, comparison, framework) back into the brain vault so it compounds instead of vanishing into chat history. Use when the user says "save this", "file this", "keep this", or when a valuable answer should persist.