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/pvliesdonk/markdown-vault-mcpWrote 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/agents/pvliesdonk/markdown-vault-mcp/vault-mapper)<a href="https://agentmods.dev/agents/pvliesdonk/markdown-vault-mcp/vault-mapper"><img src="https://agentmods.dev/badge/agents/pvliesdonk/markdown-vault-mcp/vault-mapper.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.1 | $0.00043 | $0.00266 |
| Opus 5 | $0.00022 | $0.00133 |
| Sonnet 5 | $0.00009 | $0.00053 |
| Haiku 4.5 | $0.00004 | $0.00027 |
Grade A, and why
vault-mapper 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.
What it actually says
You summarize notes from a markdown vault. Call read(path=...) for each
path assigned to you. The notes provided are one part of a larger
collection; other parts are summarized separately by other mappers.
Produce a detailed partial summary of your assigned notes that preserves
concrete specifics — names, dates, numbers, decisions, open questions — and
reference each note by its path (e.g. folder/note.md) so the partial
summaries can be combined without losing attribution. Be faithful to the
notes and do not invent details. If a note is unreadable, skip it and name
it at the end.
You may read one directly referenced note beyond your batch when needed to
resolve an otherwise-unclear reference, but summarize only your assigned
batch. If a focus was given, steer the summary toward it.
Output only the partial summary — no meta-commentary, no preamble.
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 · 23 lines · 43 tokens per session scan A bf991e47eaf7
vault-mapper is an agent published in the GitHub repository pvliesdonk/markdown-vault-mcp (32 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 266 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-30.
Other agents, from other repositories
Knowledge Linker
Scans vault for unlinked notes and suggests wikilink connections between related content.
architecture-reviewer
Wave 3 agent: analyzes module boundaries, dependency patterns, and layering decisions across the entire codebase. Produces system-level architectural memories linked with LEADSTO, DEPENDSON, BLOCKS, and CONTRADICTS relationships.
backlink-manager
Maintain wiki backlinks — update reverse index, related fields, and detect unlinked mentions after page creation/update.
context-researcher
On-demand research agent that decomposes queries into multiple search angles, runs parallel memory lookups, and synthesizes a structured briefing. Use when deep memory context is needed for a topic, entity, or decision.
wiki-auditor
Wiki health audit — finds and fixes broken links, missing frontmatter, orphans, near-duplicates. Fixes inline, no report file.
module-scanner
Searches the vault's wiki modules and identifies which ones need updates based on new transcripts. Applies a topic-based or entity-based strategy. Used by /process-transcripts.