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/write-bundle)<a href="https://agentmods.dev/commands/tboome33/obsidian-mcp-router/write-bundle"><img src="https://agentmods.dev/badge/commands/tboome33/obsidian-mcp-router/write-bundle.svg" alt="Measured on agentmods" 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.00058 | $0.00366 |
| Opus 5 | $0.00029 | $0.00183 |
| Sonnet 5 | $0.00012 | $0.00073 |
| Haiku 4.5 | $0.00006 | $0.00037 |
Grade A, and why
write-bundle 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 today.
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 write-bundle skill.
Required: steps — an ordered array of { op, path, ...args }, at most 25. op ∈ write | append | patch | set_frontmatter | merge_frontmatter | delete (a delete step still needs confirm: true).
Optional: vault (omit for default — a bundle is single-vault), preview: true (sealed plan, writes nothing, and flags any ifMatch that is already stale), approvedPlanSha256, per-step ifMatch (checked for the whole group before the first write), recover: true (list unfinished bundles) or recover: "op-<hex>" + confirm: true (+ optional only: [paths], + expect: { path: currentSha256 | null } copied from the listing — required on a vault list_vaults reports as writesRequireIfMatch: true) to replay a rollback. On such a vault every ordinary step needs ifMatch (or ifNew: true on a write step), or pass the preview's approvedPlanSha256.
Read outcome before reporting: applied · rolled-back · rolled-back-unverified (everything is back, but the undo could not be proven) · rolled-back-partial (say so plainly, and name what rollback.paths left dirty).
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.
- today Changed 138e91bb1749
- 7d ago First seen · 12 lines · 58 tokens per session scan A c95efb15a96d
write-bundle is a command published in the GitHub repository tboome33/obsidian-mcp-router (1 stars, last pushed today), licensed Apache-2.0. It adds 58 tokens to every session and 366 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
okf
A command that exports a private knowledge wiki into an OKF-compatible bundle. OKF is a format for packaging knowledge, with a separate guarded mode for preparing material to share externally.
ingest
Ingest a source (URL/file/text) into Raw Sources + compile 1015 Wiki pages, with mandatory user-purpose gate and mothership cross-linking.
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).
capture-tabs
Capture a Chrome research tab group or AI-chat research session into LLM Wiki Inbox markdown, then optionally route it through /inbox or /ingest.
init
Scaffold a new MindBase project (v2 layout). Usage: /mb:init [template] [-- mission ...].
wikimate-lint
A read-only health check for an Obsidian vault, a folder of linked Markdown notes. It scans for duplicate notes, broken links, orphaned notes, frontmatter problems, and incomplete indexes.