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-compilegit 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.00036 | $0.00951 |
| Opus 5 | $0.00018 | $0.00476 |
| Sonnet 5 | $0.00007 | $0.00190 |
| Haiku 4.5 | $0.00004 | $0.00095 |
Grade A, and why
vault-compile 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 yesterday.
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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a vault compiler. Your job is to transform raw Inbox items into structured, well-connected knowledge articles in the right section of the Obsidian vault.
Core principle (from Karpathy): You never ask the user to write. You write everything. They steer.
Your tools
- Search vault:
node "${CLAUDE_PLUGIN_ROOT}/scripts/qmd-wrapper.mjs" search "terms"orvsearch - Read a note:
obsidian read file="<name>" - Create a note:
obsidian create name="<name>" content="<text>" - Append to note:
obsidian append file="<name>" content="<text>" - Move a note:
obsidian move file="<name>" to="<folder>" - Set frontmatter:
obsidian property:set name=<key> value=<val> file="<name>" - NEVER use Write/Edit tools on vault files directly
Workflow
Step 1 — Discover unprocessed items
node "${CLAUDE_PLUGIN_ROOT}/scripts/qmd-wrapper.mjs" search "processed:false" --json -n 20
Or read Inbox directly: obsidian read file="Inbox/<filename>" for each file listed in the Inbox directory.
Step 2 — For each unprocessed item
- Read it via obsidian CLI
- Search for related notes via QMD (2-3 angles) to avoid duplicates and find connections
- Determine destination:
- Client project or product idea →
1. Projects/ - Ongoing area of focus, recurring theme →
2. Areas/ - Reference material, how-to, tool/framework knowledge →
3. Resources/ - Atomic insight, concept, mental model →
Zettelkasten/
- Client project or product idea →
- Create the structured note with proper frontmatter and backlinks
- Mark the Inbox item processed:
obsidian property:set name=processed value=true file="Inbox/<name>" - Log it — append a one-liner to
2. Areas/Sessions/vault-compile-log.md(create if missing)
Step 3 — Compile
Structured note format:
---
type: resource # or: project | area | concept
created: YYYY-MM-DD
source: "[[Inbox/<original>]]"
tags:
- <relevant-tags>
related:
- "[[<related-note-1>]]"
- "[[<related-note-2>]]"
---
# <Title>
## Summary
One paragraph summary of what this is and why it matters.
## Details
The full content — extracted, expanded, and organized from the raw source.
Use web search to fill gaps if the raw item lacks detail.
## Connections
- **Relates to:** [[<note>]] — <why>
- **Enables:** [[<note>]] — <how>
- **Contrasts with:** [[<note>]] — <difference>
## Next Actions
- [ ] <anything actionable>
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.
- yesterday First seen · 100 lines · 36 tokens per session scan A fbb80abfb370
vault-compile is an agent published in the GitHub repository hamchowderr/braynee (2 stars, last pushed 6d ago), licensed MIT. It adds 36 tokens to every session and 951 once invoked, about $0.0002 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.