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 pvliesdonk/markdown-vault-mcp --skill tool-registrationgit 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/skills/pvliesdonk/markdown-vault-mcp/tool-registration)<a href="https://agentmods.dev/skills/pvliesdonk/markdown-vault-mcp/tool-registration"><img src="https://agentmods.dev/badge/skills/pvliesdonk/markdown-vault-mcp/tool-registration/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/pvliesdonk/markdown-vault-mcp/tool-registration"><img src="https://agentmods.dev/badge/skills/pvliesdonk/markdown-vault-mcp/tool-registration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00037 | $0.01112 |
| Opus 5 | $0.00018 | $0.00556 |
| Sonnet 5 | $0.00007 | $0.00222 |
| Haiku 4.5 | $0.00004 | $0.00111 |
Grade A, and why
tool-registration 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 10d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- tool-registration — 92% identical, 10 lines differ
How it starts
The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tool Registration
Tool Registration Checklist
Every MCP tool you register must carry the full set of metadata below — not just the behaviour. A tool that works but lacks a title, hints, or docs is incomplete. When adding or changing a tool, verify each item:
- Title — a human-readable
annotations.title(e.g."Search Vault"). Title-aware clients (notably VS Code, which honours onlytitleandreadOnlyHintamong annotations) render this as the tool's label; without it they fall back to the raw machine name. Set it inline in the tool'sannotations={...}dict. - Behavioural hints —
readOnlyHint, and where they applydestructiveHint/idempotentHint, in the sameannotationsdict. These describe side effects accurately (a destructive tool must setdestructiveHint=True). - Icon — an entry wired via
register_tool_icons(...)or@mcp.tool(icons=[...])(see Tool icons). - Docstring — a Google-style docstring; FastMCP surfaces it as the tool description and per-parameter docs.
- Docs entry — a row in your published tools reference (e.g.
docs/tools/index.md) so the tool is documented for users (per the Documentation Discipline section inAGENTS.md). - Enforcement test — keep a test that enumerates the registered tools and asserts each carries the metadata above (at minimum a non-empty
annotations.title). Enumerate the full registry, not just the client-facing listing, so app-only / hidden tools cannot slip past. Such a test turns this checklist into a CI gate: a future tool added without a title fails loudly rather than silently shipping its machine name.
Tool icons
Drop SVG / PNG / ICO / JPEG files into src/markdown_vault_mcp/static/icons/ and bulk-attach them to registered tools via fastmcp_pvl_core.register_tool_icons(mcp, {"tool_name": "filename.svg"}, static_dir=...) at the end of register_tools() — or attach at decoration time with @mcp.tool(icons=[make_icon(STATIC / "x.svg")]) (where STATIC = Path(__file__).parent / "static" / "icons" is a shorthand you define at module level). The scaffold ships an empty static/icons/ directory; commented-out wiring lives in tools.py.
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.
- 10d ago First seen · 40 lines · 37 tokens per session scan A e865a4ddf6d8
tool-registration is a skill published in the GitHub repository pvliesdonk/markdown-vault-mcp (32 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 1,112 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 skills, from other repositories
mnemonic
Search local indexed markdown knowledge bases. Use when the user asks to find notes, dig up a concept from personal docs, cross-reference ideas across wikis, or answer from indexed local files. Triggers on "look up in notes", "search my docs", "what did I write about", "find in my vault", "check my index", "retrieve…
youtube-fetcher
Retrieve YouTube transcripts and subtitles, summarize or analyze what was said, or save an Obsidian-ready Markdown knowledge-base note with captions, creator metadata, chapters, language, and source provenance. Use for a YouTube URL or video ID when the request needs spoken content or an archival note. A bare YouTube…
link-memory
Use after important user-approved decisions, when durable context should be proposed or reviewed, and for explicit Link memory lifecycle work: remember, recall, review, update, archive, restore, forget, or explain local memories through the CLI without requiring MCP.
link-retrieve
Use before answering work that may depend on user memory, project history, source-backed notes, or prior decisions; retrieve compact Link context through the CLI without loading the whole wiki or requiring MCP.
link-ingest
Use when raw files are present, source pages look stale, or a user asks to ingest notes into Link; refresh source-backed wiki pages, propose memories, and validate updates through the CLI without MCP.
reduce
Extract structured knowledge from source material. Comprehensive extraction is the default — every insight that serves the domain gets extracted. For domain-relevant sources, skip rate must be below 10%. Zero extraction from a domain-relevant source is a BUG. Triggers on "/reduce", "/reduce [file]", "extract…