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 commands/vybe/project_cornelius/search-vaultgit clone --depth 1 https://github.com/vybe/project_corneliusWrote 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/commands/vybe/project_cornelius/search-vault)<a href="https://agentmods.dev/commands/vybe/project_cornelius/search-vault"><img src="https://agentmods.dev/badge/commands/vybe/project_cornelius/search-vault.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.00012 | $0.00285 |
| Opus 5 | $0.00006 | $0.00143 |
| Sonnet 5 | $0.00002 | $0.00057 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
search-vault 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.
This is a copy
100% identical to search-vault — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Quick Vault Search
Search the Obsidian vault using both semantic and keyword-based search.
Query
$ARGUMENTS
Instructions
-
Semantic Search - Use
mcp__smart-connections__search_notes:- Query: $ARGUMENTS
- Limit: 5 results
- Threshold: 0.5
-
Keyword Search - Use
Grep:- Pattern: $ARGUMENTS
- Path: /path/to/your/vault
- Output mode: "files_with_matches" to get file list
- Then use output mode: "content" with -C flag for context
-
Retrieve Content - For the top result from semantic search:
- Use
Readtool to get full content
- Use
Output Format
# Search Results: "$ARGUMENTS"
## Semantic Matches
[Top 5 notes with similarity scores]
## Keyword Matches
[Top 5 notes with context snippets from Grep]
## Top Result Content
[Full content of the most relevant note]
Keep results concise and actionable. Highlight the most relevant findings.
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 · 46 lines · 12 tokens per session scan A fc576a7b2617
search-vault is a command published in the GitHub repository vybe/project_cornelius (5 stars, last pushed 10mo ago), licensed MIT. It adds 12 tokens to every session and 285 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to search-vault, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
session-end
I'll summarize this coding session and update the memory system with our accomplishments.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.