okf-projections

okf-projections is a command for Claude Code from tboome33/obsidian-mcp-router. It costs 30 tokens per session (731 once invoked), scanned A, original, Apache-2.0.

A command for maintaining generated navigation files in an Obsidian vault, a folder of linked notes. It refreshes indexes and a change log, or checks whether they have fallen out of date.

In plain words
What is it for?
Use it to initialise a vault, rebuild its root and folder indexes, update the content history log, or produce a drift report with --check.
Why use it?
It keeps navigation files consistent after notes are changed through Obsidian or scripts, while reporting conflicts with hand-written files.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

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

Good fit Use it to initialise a vault, rebuild its root and folder indexes, update the content history log, or produce a drift report with --check.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/tboome33/obsidian-mcp-router/okf-projections
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.

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 okf-projections

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/tboome33/obsidian-mcp-router/okf-projections"><img src="https://agentmods.dev/badge/commands/tboome33/obsidian-mcp-router/okf-projections.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 731 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.00030 $0.00731
Opus 5 $0.00015 $0.00365
Sonnet 5 $0.00006 $0.00146
Haiku 4.5 $0.00003 $0.00073

Measured yesterday against content hash c8d23e0fc4ad, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

okf-projections 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 yesterday.

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.

commands/okf-projections.md · 17 lines

What it actually says

/obsidian-router:okf-projections — refresh the generated OKF navigation

Call mcp__obsidian-router__refresh_okf_projections on the target vault (parse $ARGUMENTS: an optional vault name, and --checkcheck: true).

  • What it maintains (volet ② of the 2026-07-30 catalog/journal decision): wiki/index.md (root index, frontmatter okf_version only), one index.md per content directory (* [Title](file.md) - description, grouped by type), and wiki/log.md (newest-first content history) — all derived deterministically from page frontmatter and marked > Generated by obsidian-mcp-router.
  • These files are never hand-edited and never wikilinked — internal links keep targeting [[catalog]]/[[journal]]. A hand-written file squatting a reserved path is reported as a conflict and left untouched.
  • Normally you don't need this command: the router refreshes projections automatically ~15 s after any write under wiki/ (once the vault is initialised). Use it to initialise a vault (first call), to reconcile after edits made outside the router (Obsidian, scripts), or with --check for a drift report (also part of /wiki-lint).
  • Report to the user: written/deleted/unchanged counts, any conflicts (with the explanation above), and skipped: not-initialized → propose the initialising call.
  • Also report sessions (v0.92.0+, wiki-lint's Check O): a session-folder-collision finding means content lives under BOTH wiki/Sessions/ and wiki-meta/Sessions/ — two homes for one content type; a session-folder-stray means content under wiki/Sessions/ only. wiki-meta/Sessions/ is the canonical home (the session-auto-journal hook writes there). Report, never propose a move: the wiki/ files are usually curated pages that belong in a real content area, and only the user can name it.
  • A third rule, catalog-sessions-heading (WARNING), reports the signpost rather than the misplaced file: the vault's catalogue still carries a ## Sessions AREA heading, which is what tells the next agent to file a session note under wiki/. It fires in vaults where nothing is misfiled yet — the state 16 catalogues of the fleet were in — and each finding names the file, the 1-based line and the raw heading text so the section can be found and removed. Removing it is the durable half of the repair; the catalogue should point at wiki-meta/Sessions/ instead.
  • Reading sessions.skipped: enumeration-failed / enumeration-truncated mean the check could not run — say so, never "no collision". catalog-read-failed is narrower: only the catalogue could not be read, so the heading question is open while any findings listed alongside it remain valid and must still be reported.
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. yesterday Changed · +2 lines c8d23e0fc4ad
  2. 4d ago Changed · +1 lines 7ac7645fb53b
  3. 11d ago First seen · 14 lines · 30 tokens per session scan A bc1fec1eb78e

Subscribe to this mod's changes

okf-projections is a command published in the GitHub repository tboome33/obsidian-mcp-router (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 30 tokens to every session and 731 once invoked, about $0.0002 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.