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.
npx skills add tboome33/obsidian-mcp-router --skill read-frontmattergit 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/skills/tboome33/obsidian-mcp-router/read-frontmatter)<a href="https://agentmods.dev/skills/tboome33/obsidian-mcp-router/read-frontmatter"><img src="https://agentmods.dev/badge/skills/tboome33/obsidian-mcp-router/read-frontmatter/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/skills/tboome33/obsidian-mcp-router/read-frontmatter"><img src="https://agentmods.dev/badge/skills/tboome33/obsidian-mcp-router/read-frontmatter.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.00151 | $0.00408 |
| Opus 5 | $0.00076 | $0.00204 |
| Sonnet 5 | $0.00030 | $0.00082 |
| Haiku 4.5 | $0.00015 | $0.00041 |
Grade A, and why
read-frontmatter 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.
What it actually says
read-frontmatter
Call the obsidian-router get_frontmatter MCP tool with arguments parsed from $ARGUMENTS.
Arguments
Required:
path— file path relative to vault root.
Optional:
vault— vault name. Omit for default.key— specific frontmatter property to retrieve. Omit to get the whole frontmatter object.
Argument parsing from $ARGUMENTS
- bare path →
path, returns whole frontmatter <path> <key>→path+keypath=X key=Y vault=Z
Render the result
- If a single key was requested:
<key>: <value>with the type-preserved value (number stays number, boolean stays boolean, array shown as YAML list, etc.). Ifexists: false, say so explicitly. - If the whole frontmatter was returned: show it as a YAML-formatted code block.
Note: this tool reads via application/vnd.olrapi.note+json content negotiation, so values keep their type (numbers, booleans, arrays, nested objects) — they aren't all flattened to strings.
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.
- 9d ago First seen · 39 lines · 151 tokens per session scan A d5c98baadfc6
read-frontmatter is a skill published in the GitHub repository tboome33/obsidian-mcp-router (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 151 tokens to every session and 408 once invoked, about $0.0008 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-09-03.
Other skills, from other repositories
llm-wiki-ingestion-stack
Design an ingestion and document-conversion stack for LLM-Wiki. Use when PDFs, Office files, web clips, audio/video, code repos, chats, scans, or tables must become source-preserving Markdown, or for source manifests, incremental sync, golden corpora, and ingestion evals.
llm-wiki-export-publish
Export or publish a safe subset of an LLM-Wiki as public docs, an internal handbook, a static site, llms.txt, JSONL/JSON-LD, graph export, or an archive. Use when publishing from the wiki must preserve provenance and exclude private raw sources, sensitive notes, and draft pages.
wiki-ingest
Convert trusted raw sources into reviewable LLM-Wiki pages. Use when adding PDFs, articles, transcripts, notes, repository docs, web captures, or other source material into a raw/wiki/schema vault while preserving provenance, ambiguity, links, index updates, and log entries.
llm-wiki-archive
Prepare an LLM-Wiki for long-term durability and archival. Use when the user wants a wiki to remain readable in 5-10+ years, export opaque stores, preserve raw sources, rebuild indexes, vendor key references, or create an archive manifest.
llm-wiki-doctor
Diagnose an existing vault, docs folder, repository wiki, or Markdown knowledge base before changing files. Use when the user asks what is wrong with their current notes/docs, whether they are LLM-Wiki-ready, or what the safest next step is.
llm-wiki-migration-planner
Create a no-write migration plan for turning existing notes, docs, Obsidian vaults, Notion exports, research archives, or repository documentation into an LLM-Wiki. Use when the user wants a dry-run plan before moving or editing files; route applying the approved plan to llm-wiki-refactor.