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 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/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/jzhao234/big-brain/capture"><img src="https://agentmods.dev/badge/skills/jzhao234/big-brain/capture.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.00070 | $0.00306 |
| Opus 5.5 | $0.00028 | $0.00122 |
| Sonnet 5.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 11d 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.
- 11d ago Changed c001a972c871
- 1mo ago First seen · 20 lines · 70 tokens per session scan A e21a003360f7
capture is a skill published in the GitHub repository jzhao234/big-brain (1 stars, last pushed 10d ago), licensed MIT. It adds 70 tokens to every session and 306 once invoked, about $0.0003 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-31.
Other skills, from other repositories
enzyme
Use Enzyme in an already activated Obsidian, Markdown, or Hermes workspace for working-memory retrieval, source-grounded exploration, search by keyword and meaning, runtime note-writing, and refresh. If the workspace is not initialized, follow the first-time setup section before normal retrieval.
log
Use this when a PersonalOS work session, chat outcome, personal reflection, or provided source should be persisted into the modular Daily context and any already-owned canonical files. Do NOT use for single-call processing, single-source knowledge ingestion, Gmail/WhatsApp propagation, or Lexware booking.
analyse-call
Use this when a local call transcript or meeting note should be analyzed into traceable PersonalOS context. Preserves the source, separates evidence from interpretation, updates only proven owner truth, routes confirmed commitments through task-manager, and never sends messages or triggers external actions without…
wiki-save
A tool for saving useful parts of the current conversation as organised wiki pages. It classifies the material, adds page metadata and links, and updates the wiki’s indexes and activity records.
molio-kb
Query the user's local Molio knowledge base — browse files, full-text search, read documents, and run AI Q&A grounded in the user's own notes (read-only).
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".