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 wiki-tourgit 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/wiki-tour)<a href="https://agentmods.dev/skills/tboome33/obsidian-mcp-router/wiki-tour"><img src="https://agentmods.dev/badge/skills/tboome33/obsidian-mcp-router/wiki-tour/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/wiki-tour"><img src="https://agentmods.dev/badge/skills/tboome33/obsidian-mcp-router/wiki-tour.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.00116 | $0.01189 |
| Opus 5 | $0.00058 | $0.00594 |
| Sonnet 5 | $0.00023 | $0.00238 |
| Haiku 4.5 | $0.00012 | $0.00119 |
Grade A, and why
wiki-tour 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wiki-tour
Build a guided tour through a vault: an ordered sequence of steps that teaches the vault's structure in a sensible reading order, derived from the knowledge graph's link topology (fan-in/backlinks, entry points, catalog.md sections). Reference: [[understand-anything-roadmap]] item #3.
Same split as /wiki-graph: the topology + step ordering is deterministic (the build_wiki_tour tool); you (Claude) write the pedagogical narrative — the why of each step.
Pre-condition
The knowledge graph must exist: wiki-meta/graph/knowledge-graph.json. If it doesn't, run /wiki-graph first (the tool will tell you). Richer tours come from a richer graph — suggest /wiki-refresh-digests + /wiki-graph if the vault has few digests.
Steps
1. Resolve scope
- No arg → whole-vault tour.
scopearg → one section/topic (by catalog.md heading) or a path substring. For a multi-project vault, tour one project at a time (e.g./wiki-tour Dedibox). If unsure which scopes exist, readwiki-meta/catalog.mdsection headings and offer a menu.
2. Compute the deterministic skeleton
mcp__obsidian-router__build_wiki_tour({ vault, scope?, maxSteps? })
Returns: ordered steps[] — each with order, a default title, and nodes[] ({id, name, summary}) — plus entryPoints[] and totalArticles. The skeleton is: an overview step (the entry points — highest fan-in, boosted for index/MOC names) then one step per catalog.md section (its top articles by backlink count), then a trailing "other notable pages" step for unindexed hubs.
If it warns no-articles-in-scope / no-tour-steps, tell the user the scope is empty and offer alternatives.
3. Write the pedagogical narrative (LLM — your job)
For each skeleton step, write:
- A clear step title (refine the default if needed).
- A 2-4 sentence description: what this step covers, why it matters, and how it connects to the previous step — building a coherent "what is this → how it works" arc. Ground it in the
nodes[].summaryprovided; don't invent. - Follow the vault's language convention (bilingual FR+EN if the vault is bilingual — see its
CLAUDE). - Optionally a
languageLesson-style aside for domain concepts, if useful.
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 · 71 lines · 116 tokens per session scan A 8cb8ef1e2228
wiki-tour is a skill published in the GitHub repository tboome33/obsidian-mcp-router (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 116 tokens to every session and 1,189 once invoked, about $0.0006 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
calibre-study-notes
A tool that creates study notes from books in a Calibre library for a human learner. It uses questions, recall exercises, source pointers, and optional Anki export rather than only providing a summary.
librarian
Orchestrate vault knowledge workflows using the Librarian MCP server. Ingest solutions, search prior art, explore the knowledge graph, log daily learnings.
calibre-distill
Turn ONE Calibre book into a reusable agent skill — frameworks, mental models, principles, techniques, anti-patterns, glossary, cheatsheet — by driving the calibre-mcp server (chapter map, keyword + semantic in-book search; no temp files, no Python). Use when the user wants to study a Calibre book through Claude Code…
build-interactive-explainers
A guide for building interactive explainers, calculators, and simulations driven by an executable model. Users change inputs, steps, states, or events to understand a rule or see how a process develops over time.
skill-creation-walkthrough
Step-by-step guide for creating your own Claude Skills, from deciding whether a skill is the right tool to writing the SKILL.md file, structuring reference material, and making it trigger reliably. Use when you want to package a workflow, framework, or repeated task into a reusable Skill, when an existing skill is not…
bq-skill
A coaching workflow for building a reusable library of truthful stories for behavioral job interviews. It uses structures such as STAR—Situation, Task, Action, Result—and can connect stories to a job description and résumé.