What is meta-attach-vault?

An interactive setup tool for connecting an Obsidian vault, which is a folder of Markdown notes, to a coding workspace.

Use it to attach an existing vault, create a standalone vault, or register a remote vault, including related environment, plugin, documentation, and ignore-file setup.

It handles the configuration needed to keep project notes connected while protecting credentials and setting up the note structure.

meta-attach-vault — Command for Claude Code by tboome33

Install

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.

Clone the repo

git clone --depth 1 https://github.com/tboome33/obsidian-mcp-router

Made for: Claude Code.

Or install obsidian-router, the plugin that ships this one along with the rest of its 49 skills, 54 commands, 2 agents, 3 hooks, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/tboome33/obsidian-mcp-router/meta-attach-vault/github.svg)](https://agentmods.dev/commands/tboome33/obsidian-mcp-router/meta-attach-vault)

Your own site

<a href="https://agentmods.dev/commands/tboome33/obsidian-mcp-router/meta-attach-vault"><img src="https://agentmods.dev/badge/commands/tboome33/obsidian-mcp-router/meta-attach-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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/tboome33/obsidian-mcp-router/meta-attach-vault"><img src="https://agentmods.dev/badge/commands/tboome33/obsidian-mcp-router/meta-attach-vault.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 67 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,210 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00067	$0.01210
Opus 5	$0.00034	$0.00605
Sonnet 5	$0.00013	$0.00242
Haiku 4.5	$0.00007	$0.00121

Measured 10d ago against content hash a4a1b5f30018, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

meta-attach-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 10d 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.

commands/meta-attach-vault.md · 49 lines

How it starts

The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.

meta-attach-vault

Interactive wizard that bundles the full setup of an Obsidian vault for use with obsidian-mcp-router. The dominant case is workspace-first: you're in a code/dev project (with or without .git/), and you want a vault attached to it for documentation/notes — the vault lives OUTSIDE the workspace, the workspace's .env gets a binding line, and your .gitignore is updated to protect credentials.

🔗 Vault already registered? Skip the wizard. obsidian-mcp-router --attach <slug> [--also <slug>]... (run from the workspace) does the four workspace writes in one idempotent command — .env, .claude/settings.json (the plugin toggle, without which the .env is inert), a CLAUDE.md block naming the vaults, .gitignore. Nothing is provisioned. The skill's Step 0.0 short-circuits here automatically.

Three flows, one wizard:

Workspace-first (common) — vault attached to the current code workspace via OBSIDIAN_ROUTER_DEFAULT_VAULT in .env. Default vault path: C:\VAULTS\<basename-cwd>.
Standalone vault (rare) — vault not tied to any project (personal journal style).
Remote vault — vault already runs elsewhere (NAS, VPS, Cloudflare Tunnel), just needs registration.

The skill is didactic by design: every Bash call is preceded by a 2-3 line explanation of what's about to happen, and Bash descriptions are full sentences in plain language (not cryptic command labels).

What the wizard does

For the workspace-first flow (Roland's ~95% case):

Detects context (cwd has .git/? .obsidian/? OBSIDIAN_ROUTER_DEFAULT_VAULT already set?).
If no .git/ in the workspace, explains what git is for (in plain words: versioning, secrets protection, sharing) and offers git init.
Proposes a default vault path (C:\VAULTS\<basename-cwd-as-is>), modifiable.
Runs setup-vault.mjs <vault-path> --link-workspace <cwd> (single call, single permission prompt) to: install 5 plugins, allocate a port, generate an API key, scaffold the wiki structure (wiki/, wiki/sessions/, 4 wiki-meta/ files), write .env and .mcp.json, register in the router config, AND bind the workspace to the vault via OBSIDIAN_ROUTER_DEFAULT_VAULT in <cwd>/.env.
Edits the workspace's .gitignore to add .env and .mcp.json under a marker comment (idempotent).
Conventions picker via AskUserQuestion multiSelect: the 8 installable conventions (roadmap-discipline, default-vault-health-check, wiki-query-first, path-disambiguation pre-checked; source-type, bilingual, heading-hierarchy, auto-enrichment opt-in). Installs via /obsidian-router:conventions install <id> so the H2-heading idempotency guard fires.
Final reminders: open the vault in Obsidian (with the openUri from list_vaults — pre-encoded for spaces/accents) + restart Claude Code in this workspace.

Read the full file on GitHub · 49 lines

Changes

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.

10d ago First seen · 49 lines · 67 tokens per session scan A a4a1b5f30018

Subscribe to this mod's changes

meta-attach-vault is a command published in the GitHub repository tboome33/obsidian-mcp-router (1 stars, last pushed today), licensed Apache-2.0. It adds 67 tokens to every session and 1,210 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.

Claude Code Memory and context anthropic claude-desktop karpathy knowledge-management llm-wiki

meta-attach-vault

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

meta-attach-vault

What the wizard does

What this file has done since we first saw it

Other commands, from other repositories

wiki-query

wiki-req

wiki-ingest

wiki-record

wiki-retro

wiki-discover