meta-audit-bridge-readiness

meta-audit-bridge-readiness is a skill for Claude Code from tboome33/obsidian-mcp-router. It costs 0 tokens per session (1,670 once invoked), scanned A, original, Apache-2.0.

A read-only audit of whether Obsidian files can be opened directly through clickable links. It checks the required plugins, server settings, and live HTTP route in each vault.

In plain words
What is it for?
Use it to diagnose and verify click-to-open links from chat or other tools into Obsidian vault files.
Why use it?
It finds cases where configuration files look correct but Obsidian has not actually registered the route. This explains why a click-to-open link may fail or be rejected.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths.

Part of the obsidian-router plugin — 49 skills, 54 commands, 2 agents, 3 hooks, 1 MCP server shipped together

Good fit Use it to diagnose and verify click-to-open links from chat or other tools into Obsidian vault files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tboome33/obsidian-mcp-router/meta-audit-bridge-readiness
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.

Any agent
npx skills add tboome33/obsidian-mcp-router --skill meta-audit-bridge-readiness
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.

agentmods badge for meta-audit-bridge-readiness

README.md
[![agentmods](https://agentmods.dev/badge/skills/tboome33/obsidian-mcp-router/meta-audit-bridge-readiness/github.svg)](https://agentmods.dev/skills/tboome33/obsidian-mcp-router/meta-audit-bridge-readiness)
Your own site
<a href="https://agentmods.dev/skills/tboome33/obsidian-mcp-router/meta-audit-bridge-readiness"><img src="https://agentmods.dev/badge/skills/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.

agentmods 80×15 button for meta-audit-bridge-readiness

Your own site · 80×15
<a href="https://agentmods.dev/skills/tboome33/obsidian-mcp-router/meta-audit-bridge-readiness"><img src="https://agentmods.dev/badge/skills/tboome33/obsidian-mcp-router/meta-audit-bridge-readiness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,670 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01670
Opus 5 $0.00000 $0.00835
Sonnet 5 $0.00000 $0.00334
Haiku 4.5 $0.00000 $0.00167

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

Security

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 9d 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.

skills/meta-audit-bridge-readiness/SKILL.md · 99 lines

How it starts

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

meta-audit-bridge-readiness

Diagnostic read-only de la fonctionnalité click-to-open (http://127.0.0.1:<port>/open/<path> qui ouvre un fichier dans Obsidian). C'est le complément de [[meta-status]] : meta-status vérifie que le router peut joindre chaque vault ; ce skill-là vérifie que les liens cliquables que tu mets dans le chat fonctionnent vraiment.

Quatre prérequis sont checkés par vault :

# Check Si KO
1 mcp-router-bridge plugin ≥ v0.2.0 installé route handler /open/* absent → npm run deploy:all dans le bridge repo
2 obsidian-local-rest-api plugin ≥ v4.0.0 installé méthode addPublicRoute() absente → update via Settings Community Plugins, ou copy v4.x dans .template + --sync-all --force
3 enableInsecureServer: true + insecurePort set dans .obsidian/plugins/obsidian-local-rest-api/data.json serveur HTTP non-chiffré coupé → AV (Bitdefender etc.) va dropper les HTTPS auto-signés silencieusement
4 Live probe : GET http://127.0.0.1:<insecurePort>/open/__nonexistent__.md retourne 404 (= route enregistrée) plutôt que 401 (= middleware auth catch-all = route pas registered) Obsidian a du code stale en mémoire → Ctrl+P → "Reload app without saving"

Le check #4 est le plus important — c'est lui qui détecte le cas où les fichiers sur disque sont corrects mais Obsidian tourne encore avec l'ancien code (n'a pas reload depuis le sync). Les checks 1-3 sont des static-version checks.

Steps

  1. Run the audit script and capture its JSON output:

    node "<router-repo>/scripts/meta-audit-bridge-readiness.mjs" --json
    

    (or for a single vault: --vault <slug-or-path>)

  2. Parse the JSON. Schema:

    {
      "minBridge": "0.2.0",
      "minLra": "4.0.0",
      "results": [
        {
          "vaultName": "DEDIBOX",
          "vaultPath": "C:\\VAULTS\\DEDIBOX",
          "httpsPort": 27131,
          "insecurePort": 27141,
          "bridgeVersion": "0.2.0",
          "lraVersion": "4.0.2",
          "enableInsecureServer": true,
          "checks": {
            "bridgeInstalled": true,
            "bridgeOk": true,
            "lraInstalled": true,
            "lraOk": true,
            "insecureEnabled": true,
            "routeLive": true,
            "probeResult": { "status": 404, "error": null }
          },
          "ready": true
        }
      ],
      "summary": { "total": 10, "ready": 3, "notReady": 7 }
    }
    

Read the full file on GitHub · 99 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.

  1. 9d ago First seen · 99 lines · 0 tokens per session scan A fea6930bd27d

Subscribe to this mod's changes

meta-audit-bridge-readiness is a skill published in the GitHub repository tboome33/obsidian-mcp-router (1 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,670 tokens. 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-09-03.