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-graphgit 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-graph)<a href="https://agentmods.dev/skills/tboome33/obsidian-mcp-router/wiki-graph"><img src="https://agentmods.dev/badge/skills/tboome33/obsidian-mcp-router/wiki-graph/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-graph"><img src="https://agentmods.dev/badge/skills/tboome33/obsidian-mcp-router/wiki-graph.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.00121 | $0.01531 |
| Opus 5 | $0.00060 | $0.00766 |
| Sonnet 5 | $0.00024 | $0.00306 |
| Haiku 4.5 | $0.00012 | $0.00153 |
Grade A, and why
wiki-graph 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 8d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wiki-graph
Assemble a typed knowledge graph from a vault's wiki and write it as JSON. The graph uses the Understand-Anything schema verbatim (Lum1104/Understand-Anything) so it can be visualised directly in that plugin's dashboard — see "Viewing it" below. Reference: [[understand-anything-roadmap]] item #1.
This skill is the deterministic core (--deterministic-only semantics): it maps existing vault data into a graph with no LLM calls. The LLM enrichment layers (auto-generating missing digests, discovering builds_on/contradicts edges) and Louvain community detection are roadmap follow-ons, not in this version.
What it produces
A knowledge-graph.json written to two locations:
| Path | Role |
|---|---|
wiki-meta/graph/knowledge-graph.json |
Canonical source of truth — read by the future native viewer, agents, get_wiki_context_pack. |
.understand-anything/knowledge-graph.json |
Derived copy — read directly by Understand-Anything's /understand-dashboard (zero extra step). |
Both files are byte-identical. The derived copy is regenerated each run.
How the graph is built (deterministic)
| Vault data | → Graph |
|---|---|
each wiki/ page |
article node (with knowledgeMeta: wikilinks, frontmatter) |
digest concepts (wiki-meta/digests/) |
entity nodes (deduped globally) + related edges |
digest claims |
claim nodes (page-namespaced) + related edges |
[[wikilinks]] between pages |
related edges |
referenced sources — frontmatter sources:, ^[file:42-58] citations, ![[x.pdf]] embeds |
source nodes (lightweight, unparsed) + cites edges |
wiki-meta/catalog.md sections |
topic nodes + categorized_under edges + layers[] |
Key invariant (the binaries rule): a file a page references becomes a source node even if it matches .wikiignore. .wikiignore excludes files from becoming content (article nodes / lint / export), NOT from being referenceable as sources. So you can always trace a page back to its PDF/image and click through to it.
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.
- 8d ago First seen · 109 lines · 121 tokens per session scan A ef773f12740e
wiki-graph is a skill published in the GitHub repository tboome33/obsidian-mcp-router (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 121 tokens to every session and 1,531 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
librarian
Orchestrate vault knowledge workflows using the Librarian MCP server. Ingest solutions, search prior art, explore the knowledge graph, log daily learnings.
llm-wiki
Build and maintain a persistent, interlinked Obsidian-compatible markdown wiki using Karpathy's LLM Wiki pattern. Extension-backed with auto-generated metadata, guardrails, and 14 custom tools (+3 opt-in agent-trajectory tools).
llm-wiki
Build and maintain an LLM-curated personal knowledge base — the "LLM Wiki" pattern from Andrej Karpathy's April 2026 gist. Use this skill whenever the user wants to ingest a source (paper, article, transcript, PDF, notes) into a persistent compounding knowledge base, ask a question against accumulated notes, lint or…
mindbase
Maintain a persistent AI-tended research wiki. Activates when the user wants to ingest a source (PDF, URL, article, paste), capture a thought, build the wiki context, query what's already known, lint for orphans/contradictions, or maintain page conventions. Phrases include "add this to my wiki", "today I decided…"…
bastra-recall
Persistent external brain for ChatGPT, Codex, Claude, and other MCP clients — documents (PDFs, contracts, scans with OCR), personal facts (appointments, decisions, items, amounts), AND code lessons / preferences / project topology. USE PROACTIVELY in three modes. (1) RECALL — whenever the user asks about anything from…
bastra-recall
Proactive private local memory for ChatGPT and Codex — recall before acting, save durable rules, lessons and decisions without being asked. Requires the local bastra-recall MCP server installed by bastra install codex.