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/wiki-ingest)<a href="https://agentmods.dev/commands/tboome33/obsidian-mcp-router/wiki-ingest"><img src="https://agentmods.dev/badge/commands/tboome33/obsidian-mcp-router/wiki-ingest/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/wiki-ingest"><img src="https://agentmods.dev/badge/commands/tboome33/obsidian-mcp-router/wiki-ingest.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.00042 | $0.00259 |
| Opus 5 | $0.00021 | $0.00130 |
| Sonnet 5 | $0.00008 | $0.00052 |
| Haiku 4.5 | $0.00004 | $0.00026 |
Grade A, and why
wiki-ingest 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 12d 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-ingest skill on the source(s) provided.
Source forms accepted:
- URL:
wiki-ingest https://... - Local file:
wiki-ingest /path/to/file.md - Multiple in one go:
wiki-ingest url1 url2 url3→ fan out via sub-agent - Pasted text: the user pastes a block and says "ingest this"
For URLs, prefer running the defuddle skill first if the page looks like a typical webpage with chrome (blog post, news article, docs site).
Always:
- Show the page plan (what entities/concepts will be created or updated) BEFORE writing files.
- Use
mcp__obsidian-router__write_fileandpatch_file(multi-vault aware), not native Write/Edit. - Update
wiki-meta/catalog.md,wiki-meta/journal.md,wiki-meta/hot.mdafter each successful ingestion. - Be selective — don't create a page for every passing mention.
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.
- 12d ago First seen · 20 lines · 42 tokens per session scan A dc5676d949a4
wiki-ingest is a command published in the GitHub repository tboome33/obsidian-mcp-router (1 stars, last pushed today), licensed Apache-2.0. It adds 42 tokens to every session and 259 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.
Other commands, from other repositories
wiki-query
Ask questions against the wiki. Synthesizes answers from wiki pages with cross-reference citations.
wiki-req
Capture and decompose a concept into atomic, traceable wiki requirements. Clarifies ambiguous requirements, splits them into atomic pieces, and persists them as wiki/requirements/ pages with status tracking.
wiki-ingest
Process new source packets and synthesize them into wiki knowledge pages.
wiki-record
Capture the just-completed task's tool-call trajectory into the wiki as agent working-memory, then optionally distill it into a reusable skill.
wiki-retro
Save an atomic insight from the current task into the wiki. Creates a single markdown file that layered recall surfaces in future sessions.
wiki-run
Run the full wiki cycle: discover → ingest → lint. Optionally schedule for auto-updates.