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 thoreinstein/obsidian-rag --skill vaultgit clone --depth 1 https://github.com/thoreinstein/obsidian-ragWrote 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/thoreinstein/obsidian-rag/vault)<a href="https://agentmods.dev/skills/thoreinstein/obsidian-rag/vault"><img src="https://agentmods.dev/badge/skills/thoreinstein/obsidian-rag/vault/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/thoreinstein/obsidian-rag/vault"><img src="https://agentmods.dev/badge/skills/thoreinstein/obsidian-rag/vault.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.00032 | $0.00150 |
| Opus 5.5 | $0.00013 | $0.00060 |
| Sonnet 5.5 | $0.00006 | $0.00030 |
| Haiku 4.5 | $0.00003 | $0.00015 |
Grade A, and why
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 1mo 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 vault — 31 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
Set Vault Path
Configure the Obsidian vault path for this session.
With Argument
If the user provides a path after /vault:
- Call
obsidian_set_vaultwith the provided path
Without Argument
If no path is provided:
- Ask the user: "What is the absolute path to your Obsidian vault?"
- Once they respond, call
obsidian_set_vaultwith their path
Confirmation
After setting, confirm: "Vault path set to: [path]"
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.
- 1mo ago First seen · 26 lines · 32 tokens per session scan A 6f09961e274b
vault is a skill published in the GitHub repository thoreinstein/obsidian-rag (2 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 150 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to vault, differing in 31 lines, and is treated as a copy.
Other skills, from other repositories
acm-handoff
Use when resuming work from a previous session that reached context threshold, or when a handoff summary exists. Reads handoff state and markdown to restore context, todos, and continue seamlessly.
acm-config
Use when the user wants to customize Claudikins Automatic Context Manager behavior, configure trigger threshold, snooze duration, summary length, or runs '/acm:config'. Interactively asks questions and saves preferences to config file.
whats-up
Fetch recent activity from Autographical — what the user and their AI agents have been working on. Use when starting a session, when the user mentions recent activity, when the user alludes to what they were doing or looking at, or picking up where they left off. Also use when the conversation feels like a topic…
user-profile
Use to create or update the user's anchor profile — a single private file (/bettersense-work-reflections/profile.md) that captures who the user is, what they do, what context other skills need to know about them. Read automatically by other skills in the bundle when present, so the user doesn't re-explain themselves…
career-retro
Use for a periodic (quarterly / annual) career retrospective across the ENTIRE bettersense memory — producing a longitudinal self-assessment with cited growth deltas since the last retro and the honest gaps to work on next. Trigger phrases include "run my career retro", "where am I in my career", "annual…
doctor
Use to health-check the user's bettersense memory directory — validate the file layout, catch problems before they cost data, and set up backups. Trigger phrases include "run bettersense doctor", "check my reflection files", "is my bettersense data okay", "something seems off with my stakeholder files", "back up my…