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/okf-export)<a href="https://agentmods.dev/commands/tboome33/obsidian-mcp-router/okf-export"><img src="https://agentmods.dev/badge/commands/tboome33/obsidian-mcp-router/okf-export/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/okf-export"><img src="https://agentmods.dev/badge/commands/tboome33/obsidian-mcp-router/okf-export.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.00063 | $0.00462 |
| Opus 5 | $0.00032 | $0.00231 |
| Sonnet 5 | $0.00013 | $0.00092 |
| Haiku 4.5 | $0.00006 | $0.00046 |
Grade A, and why
okf-export 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.
What it actually says
Invoke the wiki-export skill with --target okf.
ARGUMENTS: $ARGUMENTS
Arguments (all optional): [scope] [--name <bundle-name>] [--readme-agent] [--vault <slug>]
scope— what to export: a folder (wiki/Divers), a tag filter (#trading), or nothing for the wholewiki/tree. When ambiguous, ask the user which subset they want to share BEFORE fetching pages.--name— bundle folder name; default: slugified vault name.--readme-agent— also emit the self-installing README (agent onboarding prompt, Cole Medin pattern). Recommend it when the bundle will be published.
Default behaviour:
- Output: a complete OKF v0.1 bundle under
wiki-meta/exports/okf/<name>/inside the vault — one file per page + oneindex.mdper folder + newest-firstlog.md. Self-contained: the user can copy it anywhere,git init && git pushit, or hand it to any OKF-aware agent. wiki-meta/content (hot, digests, sessions, graph) is NEVER exported — private working data.- The vault itself is untouched (read-only on
wiki/; the export lands underwiki-meta/exports/). - Conformance self-check (
checkOkfConformance) MUST pass with zero errors before writing anything — an error means an exporter bug, report it instead of shipping a broken bundle. - Always surface the export report: renamed files (reserved names, slug collisions), dangling links (legal — "not-yet-written knowledge"), dropped anchors, demoted embeds.
Decision context: OKF is our exchange format at the edges — internal vault structure never changes (vault page okf-interop, 2026-07-03).
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 · 22 lines · 63 tokens per session scan A 79942e924302
okf-export is a command published in the GitHub repository tboome33/obsidian-mcp-router (1 stars, last pushed today), licensed Apache-2.0. It adds 63 tokens to every session and 462 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.