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 jenningsallen-art/second-brain-os --skill vault-capturegit clone --depth 1 https://github.com/jenningsallen-art/second-brain-osWrote 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/jenningsallen-art/second-brain-os/vault-capture)<a href="https://agentmods.dev/skills/jenningsallen-art/second-brain-os/vault-capture"><img src="https://agentmods.dev/badge/skills/jenningsallen-art/second-brain-os/vault-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/jenningsallen-art/second-brain-os/vault-capture"><img src="https://agentmods.dev/badge/skills/jenningsallen-art/second-brain-os/vault-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.00133 | $0.02042 |
| Opus 5 | $0.00067 | $0.01021 |
| Sonnet 5 | $0.00027 | $0.00408 |
| Haiku 4.5 | $0.00013 | $0.00204 |
Grade A, and why
vault-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.
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vault Capture
Capture knowledge into the user's Obsidian second brain vault. The goal is to make this effortless — like jotting something in a notebook, not filling out a form.
For the user's working style, people, and session-level vault rules: read CLAUDE.md in the vault root. This skill defines the structural rules for how notes are created, named, filed, and maintained.
Finding the Vault
Look for these indicators:
- A
CLAUDE.mdin the workspace root mentioning "Obsidian" or "vault" - PARA folders (
0 - Inbox/,1 - Projects/, etc.) .obsidian/directory
If the workspace IS the vault, write directly. If not, save .md files to the workspace and tell the user to move them to their vault Inbox.
Vault Structure
Folder Semantics (PARA)
| Folder | Purpose | What goes here |
|---|---|---|
0 - Inbox/ |
Landing zone | New notes when you're not sure where they belong. Refile later. |
1 - Projects/ |
Active work with a defined outcome | Canonical strategy docs, project specs, active build plans. |
2 - Areas/ |
Ongoing responsibilities + meetings | Meeting notes (YYYY-MM-DD Title.md), identity docs, recurring context. Non-dated area docs (Active Priorities, identity notes) also live here. |
3 - Resources/ |
Reference material | People profiles, frameworks, decision records, tools, reference data. All people at top level — no subfolders. |
4 - Archive/ |
Superseded, completed, or routine | Organized by category subfolders. Every archived file keeps its backlinks and gets a superseded marker. |
Naming Conventions
| Type | Pattern | Example |
|---|---|---|
| People | First Last.md |
Jane Doe.md |
| Meetings | YYYY-MM-DD Title.md |
2026-04-10 Weekly 1v1.md |
| Projects/Concepts | Descriptive title, no version numbers | AI Operations — Canonical.md (not AI Ops v6.md) |
| Decisions | Decision - [What was decided].md |
Decision - Google Sheets as Data Layer.md |
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 First seen · 169 lines · 133 tokens per session scan A 06611953ec67
vault-capture is a skill published in the GitHub repository jenningsallen-art/second-brain-os (2 stars, last pushed 1mo ago), licensed MIT. It adds 133 tokens to every session and 2,042 once invoked, about $0.0007 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…
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…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.