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.
git clone --depth 1 https://github.com/tboome33/obsidian-mcp-routerWrote 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/tboome33/obsidian-mcp-router/meta-sync-template)<a href="https://agentmods.dev/commands/tboome33/obsidian-mcp-router/meta-sync-template"><img src="https://agentmods.dev/badge/commands/tboome33/obsidian-mcp-router/meta-sync-template/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/commands/tboome33/obsidian-mcp-router/meta-sync-template"><img src="https://agentmods.dev/badge/commands/tboome33/obsidian-mcp-router/meta-sync-template.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.00075 | $0.00733 |
| Opus 5 | $0.00037 | $0.00367 |
| Sonnet 5 | $0.00015 | $0.00147 |
| Haiku 4.5 | $0.00007 | $0.00073 |
Grade A, and why
meta-sync-template 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.
How it starts
The opening of the file, as written. The whole thing — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
meta-sync-template
Interactive bulk propagation of the reference vault (typically .template) to one or more configured vaults. Conversational picker over scripts/setup-vault.mjs's --sync-all and --sync-plugins modes.
The safety guarantees are enforced by the script itself (obsidian-mcp-router v0.11.2+): the reference vault is auto-skipped via a case-insensitive samePath() match (Windows NTFS / macOS APFS safe), and first-time copies of credentialed plugins (currently obsidian-local-rest-api) into vaults that don't have them yet are refused to prevent API-key leaks. The skill's job is purely UX.
Follow the steps in the meta-sync-template skill. The skill:
- Locates the cloned
obsidian-mcp-routerrepo (CWD →npm root -g→npm ls -g --parseable→ ask the user). - Reads the active router config (
list_vaults.configPath, respectingOBSIDIAN_ROUTER_CONFIG). - Calls
list_vaultsto probe online status (informational — sync works offline too). - Renders a picker table flagging targets that lack
obsidian-local-rest-api/data.jsonwith⚠️ needs bootstrapso the user can prep them first. Asks: All vaults, subset, or cancel. - Asks whether to pass
--force(re-clone every plugin folder). - Runs
npm run setup-vault -- --sync-all [--force]for the all-vaults case (the script's bulk handler iterates safely). For a subset, loopsnode scripts/setup-vault.mjs "<path>" --sync-plugins [--force]over the user's selection. - Aggregates per-vault results and reminds the user that any vault currently open in Obsidian needs a reload (Ctrl+R / Cmd+R) to pick up newly synced plugins.
The sync is filesystem-based — offline vaults are propagated too. Per-vault obsidian-local-rest-api/data.json (port + API key) is preserved across re-clones for vaults that already have the plugin (setup-vault.mjs:835-842); for vaults without it, the script refuses the copy with a clear "bootstrap first via setup-vault.mjs "<path>"" message.
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 · 35 lines · 75 tokens per session scan A 06b2c9f88b1d
meta-sync-template is a command published in the GitHub repository tboome33/obsidian-mcp-router (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 75 tokens to every session and 733 once invoked, about $0.0004 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 commands, from other repositories
wiki-query
Ask questions against the wiki. Synthesizes answers from wiki pages with cross-reference citations.
wiki-digest
Generate a daily or weekly digest of wiki changes — new sources, pages, insights, and gaps.
wikimate-link
A command for connecting related Obsidian notes with [[links]] or grouping notes into a topic table of contents, also called a MOC. Obsidian is an app for storing linked Markdown notes.
gws-keep
List and read Google Keep notes.
agenda
Show upcoming calendar events.
brief
Cold-start session orientation — use when starting fresh or returning after a long absence (days or weeks). Scales depth to how long you've been away. Not for quick mid-session checks (use /tools:status) or planning (use /tools:overview).