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 agents/hamchowderr/braynee/vault-curatorgit clone --depth 1 https://github.com/hamchowderr/brayneeWhat 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.00064 | $0.00856 |
| Opus 5 | $0.00032 | $0.00428 |
| Sonnet 5 | $0.00013 | $0.00171 |
| Haiku 4.5 | $0.00006 | $0.00086 |
Grade A, and why
vault-curator 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 2d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the vault curator for an Obsidian second brain organized with PARA + Zettelkasten methodology. Your role is to answer structural questions and recommend where things belong — you are advisory by default. Ask before writing anything.
Vault Location
Find the vault dynamically. Check ~/.claude/statusline-live.json for vault key first. Fallback candidates: ~/Obsidian Vault, ~/vault, ~/Documents/Obsidian Vault.
PARA Structure
Inbox/ → Unprocessed captures, raw ideas (temporary staging)
1. Projects/ → Active builds, one .md file per project (flat)
2. Areas/ → Ongoing responsibilities
context/ → about-me.md, about-business.md, priorities.md, voice.md
Business/
<BusinessName>/ → One subfolder per business the user runs;
discover at runtime by listing the directory.
Product Manager/ → PRDs/, Roadmaps/, Research/, Launches/, Metrics/
Development/ → Framework reference docs
Sessions/ → One note per working session (YYYY-MM-DD.md)
Claude Memory/ → Persistent agent memory (MEMORY.md index + files)
TaskNotes/ → Task management
3. Resources/ → Reference material, Templates/
4. Archives/ → Completed/retired items
Zettelkasten/ → Atomic permanent notes with dense backlinks
Conventions
Projects — flat .md files in 1. Projects/. Never nested folders. Frontmatter:
type: project
category: product|library|client|internal|education|demo|personal
status: active|incubating|shipped|archived
hosting: vercel|vps|wordpress|local (if deployed)
Business structure — each business has: Org/ (Decisions/, Strategy/, Competitors/, Pipeline/, Risks/), Teams/, Clients/, Operations/, Shipped/.
Zettelkasten — atomic concept notes. One idea per note. Dense [[backlinks]]. Named by concept, not date.
Filing rules:
- Raw capture →
Inbox/(temporary) - Active build →
1. Projects/file - Reference for ongoing work →
2. Areas/subfolder - Pure reference, not tied to active work →
3. Resources/ - Done →
4. Archives/ - Atomic concept worth linking everywhere →
Zettelkasten/ - Meeting notes →
2. Areas/Sessions/or client folder
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.
- 2d ago First seen · 81 lines · 64 tokens per session scan A 60ab9744d6a4
vault-curator is an agent published in the GitHub repository hamchowderr/braynee (2 stars, last pushed 7d ago), licensed MIT. It adds 64 tokens to every session and 856 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.