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-audit-bridge-readiness)<a href="https://agentmods.dev/commands/tboome33/obsidian-mcp-router/meta-audit-bridge-readiness"><img src="https://agentmods.dev/badge/commands/tboome33/obsidian-mcp-router/meta-audit-bridge-readiness/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-audit-bridge-readiness"><img src="https://agentmods.dev/badge/commands/tboome33/obsidian-mcp-router/meta-audit-bridge-readiness.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.00068 | $0.00732 |
| Opus 5 | $0.00034 | $0.00366 |
| Sonnet 5 | $0.00014 | $0.00146 |
| Haiku 4.5 | $0.00007 | $0.00073 |
Grade A, and why
meta-audit-bridge-readiness 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 12d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
meta-audit-bridge-readiness
Read-only diagnostic of the click-to-open feature (http://127.0.0.1:<port>/open/<path> links that open files in Obsidian). Complement of meta-status: that one checks the router can reach each vault; this one checks the clickable links actually work.
Steps
-
Run the audit script with JSON output:
node "<router-repo>/scripts/meta-audit-bridge-readiness.mjs" --jsonFor a single vault: append
--vault <slug-or-path>. -
Parse the JSON and render as a table:
- Header line:
<total> vault(s) · <ready> ready · <notReady> need attention - Columns:
vault | bridge | LRA | insecure | /open route | ready? ✅ready,❌not ready
- Header line:
-
For each
ready: falsevault, surface the FIRST matching cause in this priority order, with the exact command to run:
| Failed check | Remediation |
|---|---|
!bridgeInstalled |
node scripts/setup-vault.mjs "<vaultPath>" --sync-plugins --force |
!bridgeOk (version < 0.2.0) |
In bridge repo: npm run deploy:all |
!lraInstalled |
Install Local REST API via Obsidian Settings → Community plugins |
!lraOk (version < 4.0.0) |
Update LRA via Obsidian Settings, OR copy v4.x main.js+manifest+styles into .template then node scripts/setup-vault.mjs --sync-all --force |
!insecureEnabled |
Edit .obsidian/plugins/obsidian-local-rest-api/data.json: enableInsecureServer: true + a free insecurePort |
probe ECONNREFUSED |
Obsidian not running, OR Local REST API disabled, OR insecure server toggle off |
probe HTTP 401 |
Files OK, but Obsidian has stale code in memory. Ctrl+P → "Reload app without saving" |
- Closing line:
- All ready →
🎉 All <total> vaults are click-to-open ready. - Some not ready →
Apply fixes above, then re-run /obsidian-router:meta-audit-bridge-readiness to verify.
- All ready →
Don't
- Auto-fix anything. Diagnostic only — the user picks what to reload/sync.
- Expose API keys.
- Probe HTTPS. Use the insecure HTTP port (Windows AV intercepts self-signed HTTPS loopback silently — full rationale in
wiki/obsidian-mcp-router-bridge/project-bridge.md"Troubleshooting").
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.
- 12d ago First seen · 48 lines · 68 tokens per session scan A c05b1fb42f78
meta-audit-bridge-readiness is a command published in the GitHub repository tboome33/obsidian-mcp-router (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 68 tokens to every session and 732 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 commands, from other repositories
lint
Run health check on a project — orphans, contradictions, stale claims, gaps, suggested cross-links. Usage: /mb:lint [-p ] [project-id].
doctor
A diagnostic command for checking and, when requested, repairing an llm-brain installation. It also offers read-only profiles for demo, private use, or preparing a shareable setup.
lint
Run comprehensive wiki health check — orphans, broken links, contradictions, stale pages, index sync, MOC coverage, v2/v4/v5 frontmatter coverage, Core Context freshness, and cross-vault link integrity (mainVaultRelated/mainVaultCmds).
reconnect
Diagnose the ga-mcp-full MCP connection and walk through reconnect options. Use when GA tool calls stop responding, return auth errors, or /plugin shows a red error for ga-mcp-full.
refactor-clean
You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.
wiki-query
Ask questions against the wiki. Synthesizes answers from wiki pages with cross-reference citations.