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/lock)<a href="https://agentmods.dev/commands/tboome33/obsidian-mcp-router/lock"><img src="https://agentmods.dev/badge/commands/tboome33/obsidian-mcp-router/lock/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/lock"><img src="https://agentmods.dev/badge/commands/tboome33/obsidian-mcp-router/lock.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.00057 | $0.00264 |
| Opus 5 | $0.00028 | $0.00132 |
| Sonnet 5 | $0.00011 | $0.00053 |
| Haiku 4.5 | $0.00006 | $0.00026 |
Grade A, and why
lock 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 5d 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.
What it actually says
Invoke the lock skill.
Required: the vault name to lock to.
Optional: persist (default false) — when true, records locked: true on this workspace's binding in the user's router config (what a restart reads) and writes OBSIDIAN_ROUTER_LOCKED=<vault> to <cwd>/.env as a portable hint. A lock named only by a project file is not applied at start-up, so persisted in the result is false when the config could not be written.
The skill handles:
- Argument parsing (bare name,
<name> --persist, conversational phrasing) - Verification the vault is in the active set (refuses with the known-vaults list if not)
- Default-
persist=trueinference from phrasings like "de manière permanente" - Push-back when the user is already locked to a different vault
- Homedir refusal when persisting from
~(in-memory still applies)
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.
- 5d ago Changed · +6 tokens per session 94850bcd18bf
- 9d ago First seen · 17 lines · 51 tokens per session scan A 04b6bc2aaa49
lock is a command published in the GitHub repository tboome33/obsidian-mcp-router (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 57 tokens to every session and 264 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
wiki-req
Capture and decompose a concept into atomic, traceable wiki requirements. Clarifies ambiguous requirements, splits them into atomic pieces, and persists them as wiki/requirements/ pages with status tracking.
wiki-retro
Save an atomic insight from the current task into the wiki. Creates a single markdown file that layered recall surfaces in future sessions.
wiki-discover
Auto-discover new sources from the web. Searches based on config topics and known knowledge gaps.
wiki-status
Show wiki health overview — source count, page stats, orphan count, last activity dates.
init
Scaffold a new MindBase project (v2 layout). Usage: /mb:init [template] [-- mission ...].
ask
Query the MindBase wiki — cited answer using hybrid search + graph expansion. Usage: /mb:ask [-p ] [--all-projects].