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/decision-consolidate)<a href="https://agentmods.dev/commands/tboome33/obsidian-mcp-router/decision-consolidate"><img src="https://agentmods.dev/badge/commands/tboome33/obsidian-mcp-router/decision-consolidate/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/decision-consolidate"><img src="https://agentmods.dev/badge/commands/tboome33/obsidian-mcp-router/decision-consolidate.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.00077 | $0.00268 |
| Opus 5 | $0.00039 | $0.00134 |
| Sonnet 5 | $0.00015 | $0.00054 |
| Haiku 4.5 | $0.00008 | $0.00027 |
Grade A, and why
decision-consolidate 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 11d 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 decision-consolidate skill.
Arguments: a decision page path or basename (required) · a vault name (defaults to the current/locked/default vault) · --dry-run (show what stays / what moves, write nothing).
The skill handles:
- Eligibility gate:
accepted/superseded/rejectedonly — aproposedpage is refused (its deliberation is the working material) - Archive-first transaction:
<folder>/archives/<slug>-deliberation.md(type: decision-archive) written and VERIFIED before the page is touched - Canonical compact rewrite: verdict byte-intact, minimal why, alternatives table,
consolidated:marker, mandatory## Historiquewikilink to the archive - Post-check: decision lint green (no
consolidated-*findings) + thinjournal.mdtrace
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.
- 11d ago First seen · 14 lines · 77 tokens per session scan A 0b05322fd35d
decision-consolidate is a command published in the GitHub repository tboome33/obsidian-mcp-router (1 stars, last pushed today), licensed Apache-2.0. It adds 77 tokens to every session and 268 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-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-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.
wiki-status
Show wiki health overview — source count, page stats, orphan count, last activity dates.
init
Scaffold a new MindBase project (v2 layout). Usage: /mb:init [template] [-- mission ...].
ask
Query the MindBase wiki — cited answer using hybrid search + graph expansion. Usage: /mb:ask [-p ] [--all-projects].