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 companion-inc/introspect --skill obsidian-vault-handoffgit clone --depth 1 https://github.com/companion-inc/introspectWrote 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/companion-inc/introspect/obsidian-vault-handoff)<a href="https://agentmods.dev/skills/companion-inc/introspect/obsidian-vault-handoff"><img src="https://agentmods.dev/badge/skills/companion-inc/introspect/obsidian-vault-handoff/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/companion-inc/introspect/obsidian-vault-handoff"><img src="https://agentmods.dev/badge/skills/companion-inc/introspect/obsidian-vault-handoff.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.00051 | $0.01070 |
| Opus 5 | $0.00026 | $0.00535 |
| Sonnet 5 | $0.00010 | $0.00214 |
| Haiku 4.5 | $0.00005 | $0.00107 |
Grade A, and why
obsidian-vault-handoff 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Obsidian vault handoff
Problem
You generated markdown into a folder and sent the user an obsidian://open?vault=... or obsidian://open?path=... URL. Obsidian rejected it with "Unable to find a vault for the URL" even though the folder has a .obsidian/ directory.
Obsidian's URL handler resolves vault names and paths only against its app-level registry at ~/Library/Application Support/obsidian/obsidian.json. A .obsidian/ directory inside the folder is not enough — the folder must be registered.
When to load
- About to send the user an
obsidian://open?...URI for a folder you created or moved. - The user reports "Unable to find a vault for the URL".
- You wrote markdown intended to be opened in Obsidian (
.obsidian/, wiki-links, MOC/START-HERE pages) into a path that isn't yet a known vault.
Do not load for: editing files already inside a folder that is registered in Obsidian's vault registry — those URIs already work.
Procedure
-
Read the current registry:
cat "$HOME/Library/Application Support/obsidian/obsidian.json"Confirm whether the target absolute path appears under
vaults.<id>.path. If it does, skip to step 4. -
If Obsidian is running, quit it first — a live Obsidian process rewrites
obsidian.jsonon exit and will clobber your edit:osascript -e 'tell application "Obsidian" to quit' -
Add a vault entry. The key is a random 16-hex id (Obsidian's convention), not a slug. Use a real epoch-ms timestamp. Preserve the existing entries.
python3 - <<'PY' import json, os, secrets, time, pathlib p = pathlib.Path.home() / "Library/Application Support/obsidian/obsidian.json" data = json.loads(p.read_text()) vault_path = "/absolute/path/to/folder" if not any(v["path"] == vault_path for v in data["vaults"].values()): vid = secrets.token_hex(8) data["vaults"][vid] = {"path": vault_path, "ts": int(time.time() * 1000), "open": True} p.write_text(json.dumps(data)) PY
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 · 81 lines · 51 tokens per session scan A c681f1b45fab
obsidian-vault-handoff is a skill published in the GitHub repository companion-inc/introspect (10 stars, last pushed 23d ago), licensed MIT. It adds 51 tokens to every session and 1,070 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…