Borrowing it
Nothing to install: this file belongs to pvliesdonk/markdown-vault-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/pvliesdonk/markdown-vault-mcp/main/AGENTS.mdgit 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/instructions/pvliesdonk/markdown-vault-mcp/agents-md)<a href="https://agentmods.dev/instructions/pvliesdonk/markdown-vault-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/pvliesdonk/markdown-vault-mcp/agents-md/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/instructions/pvliesdonk/markdown-vault-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/pvliesdonk/markdown-vault-mcp/agents-md.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.03820 | $0.03820 |
| Opus 5.5 | $0.01528 | $0.01528 |
| Sonnet 5.5 | $0.00764 | $0.00764 |
| Haiku 4.5 | $0.00382 | $0.00382 |
Grade A, and why
markdown-vault-mcp AGENTS.md 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 yesterday.
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
2 near-identical copies found in the catalogue:
- scholar-mcp AGENTS.md — 91% identical, 267 lines differ
- paperless-mcp AGENTS.md — 88% identical, 281 lines differ
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Markdown Vault MCP
Generic markdown vault MCP with hybrid search
Design
The authoritative design specification lives at docs/design/design.md. All implementation must conform to this spec. When in doubt, the design doc wins.
Project Structure
The complete file-by-file map of src/markdown_vault_mcp/ lives in
docs/design/module-map.md — read it when locating
a module or adding one, rather than guessing from the package layout. It is kept
out of this always-loaded file because it is reference material consulted on
demand, not context every session needs.
Conventions
- Write commit subjects and pull-request titles as conventional commits: one type from
build,chore,ci,docs,feat,fix,perf,refactor,revert,style,test, an optional scope (feat(search): ...), and!for a breaking change. ThePR Titlejob fails any other title; retitle to clear it, no push needed. Accepted types:scripts/check_pr_title.py. - Only
feat,fix, and the!marker drive releases:featcuts a minor,fixa patch,!a major. Every other type,perfincluded, cuts nothing and never reachesCHANGELOG.md. Ship a change that needs a release of its own as afix:or through Release Prepare'soverride_versioninput. Revert "..."titles pass the title job. Neither revert form reachesCHANGELOG.md; narrate a revert on itsdocs/releases/page.- Write a Google-style docstring on every public function and a type hint on every signature.
- Log through
logging.getLogger(__name__), neverprint(), with messages shapedevent_name key=%s(thelogging-standardskill);tests/test_logging_standard.pyfails any other first-party call. - Put shared test fixtures in
tests/fixtures/.
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.
- yesterday Changed · +3 lines · +228 tokens per session 5f8a3d43aa96
- 18d ago Changed · -98 lines · -2,269 tokens per session fc466e0f2a09
- 24d ago Changed · +29 tokens per session 19b3cfd0d302
- 25d ago Changed · +11 tokens per session 35af479b209f
- 27d ago Changed · +1 lines · +39 tokens per session 56ed19c2cfc4
- 28d ago Changed · +2 lines · +161 tokens per session 008950cd1ff0
- 1mo ago Changed · +2 lines · +223 tokens per session f70785d0b5f8
- 1mo ago Changed · +7 lines · +211 tokens per session 72004752e316
- 1mo ago Changed · +3 lines · +300 tokens per session 6f6a1a114f96
- 1mo ago First seen · 246 lines · 4,887 tokens per session scan A 30afc41a3641
markdown-vault-mcp AGENTS.md is an instructions file published in the GitHub repository pvliesdonk/markdown-vault-mcp (35 stars, last pushed today), licensed MIT. It adds 3,820 tokens to every session, about $0.0153 per session on Opus 5.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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.