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 agentmods add commands/tboome33/obsidian-mcp-router/sync-from-githubgit 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/sync-from-github)<a href="https://agentmods.dev/commands/tboome33/obsidian-mcp-router/sync-from-github"><img src="https://agentmods.dev/badge/commands/tboome33/obsidian-mcp-router/sync-from-github.svg" alt="Measured on agentmods" 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 | $0.00072 | $0.00239 |
| Opus 5 | $0.00036 | $0.00120 |
| Sonnet 5 | $0.00014 | $0.00048 |
| Haiku 4.5 | $0.00007 | $0.00024 |
Grade A, and why
sync-from-github 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 4d 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 sync-from-github skill.
Arguments: vault path(s) or --all (empty → interactive picker over the configured fleet) · --ref <branch|tag> (default main) · --force (re-clone plugins, preserving each local data.json).
The skill handles:
- Target picking (never chooses for the user when no target is given)
- Running
node scripts/setup-vault.mjs --sync-from-github …and reporting the four outcome categories per vault (synced / refreshed / kept-newer / refused-for-safety) - Treating safety refusals and anti-downgrade keeps as guarantees to respect, never as errors to bypass
- Reminding that touched vaults need an Obsidian reload to load new plugins
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.
- 4d ago First seen · 14 lines · 72 tokens per session scan A afc8250463c7
sync-from-github is a command published in the GitHub repository tboome33/obsidian-mcp-router (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 72 tokens to every session and 239 once invoked, about $0.0004 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-discover
Auto-discover new sources from the web. Searches based on config topics and known knowledge gaps.