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 instructions/phate45/mcp-vault/claude-mdgit clone --depth 1 https://github.com/phate45/mcp-vaultWrote 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/phate45/mcp-vault/claude-md)<a href="https://agentmods.dev/instructions/phate45/mcp-vault/claude-md"><img src="https://agentmods.dev/badge/instructions/phate45/mcp-vault/claude-md.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.00503 | $0.00503 |
| Opus 5 | $0.00251 | $0.00251 |
| Sonnet 5 | $0.00101 | $0.00101 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
mcp-vault CLAUDE.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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code when working with code in this repository.
Project Overview
MCP server for Obsidian vault operations. Communicates with Obsidian via the Local REST API plugin (custom fork required for move operations) and reads markdown files directly from the filesystem.
Project Structure
src/mcp_vault/__init__.py- Package entry pointsrc/mcp_vault/server.py- MCP server with tool registration and handlerssrc/mcp_vault/tools.py- Tool definitions usingToolHandlerbase classsrc/mcp_vault/implementation.py- Markdown parsing and heading analysis logic
Contributing Guidelines
Adding a New Tool
- Create a new class in
tools.pythat extendsToolHandler - Implement
get_tool_description()to return MCPToolobject with JSON schema - Implement
run_tool(args: dict)with the tool's logic - Register the tool in
register_tools()function by adding it to the returned dictionary
Example pattern:
class MyNewTool(ToolHandler):
def get_tool_description(self) -> Tool:
return Tool(name="my_tool", ...)
async def run_tool(self, args: dict) -> list[TextContent]:
# Implementation here
pass
Code Conventions
- All server operations use async/await
- Tools return
list[TextContent]from MCP types - File paths in arguments are relative to vault root
- Use the ToolHandler pattern for consistency
Runtime Requirements
- Python >=3.13: Required for modern type hints and async features
- Environment Variable:
VAULT_PATHmust be set to absolute path of Obsidian vault - External Dependencies:
- Obsidian Local REST API plugin (custom fork) running on localhost:27124
- API token read from
.obsidian/plugins/obsidian-local-rest-api/data.json - See README for details on the required fork for move_file functionality
Testing
TODO: No tests currently exist. Once test files are added or the testing TODO in README is addressed, update this section with:
- Testing approach and framework
- How to run tests
- Any special considerations for testing MCP tools
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.
- 5d ago First seen · 60 lines · 503 tokens per session scan A 7f36c3754f04
mcp-vault CLAUDE.md is an instructions file published in the GitHub repository phate45/mcp-vault (1 stars, last pushed 9mo ago), licensed MIT. It adds 503 tokens to every session, about $0.0025 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 instructions, from other repositories
aeon CLAUDE.md
Claude Code instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).
cognirepo CLAUDE.md
Claude Code instructions for ashlesh-t/cognirepo, covering claude.md, key rules, session start sequence (run in this order), behavioral confirmation rule and personas (cognirepo-402, cognirepo-403).
wayland-core copilot-instructions.md
Copilot instructions for FerroxLabs/wayland-core, covering ijfw rules, output discipline, memory routing, context discipline and cross-audit.
mcp-structured-memory CLAUDE.md
Claude Code instructions for nmeierpolys/mcp-structured-memory, a project described as: Structured Memory MCP Server.
inkwell-memory CLAUDE.md
Instructions for veronchenko/inkwell-memory, covering claude.md — inkwellmemory, layout, multi-tenant mode (inkwellmultitenant=1), conventions and testing.
memory-mcp-1file AGENTS.md
Instructions for pomazanbohdan/memory-mcp-1file, covering ⛔ l0 invariants (never violate under any circumstance), detection heuristic, 🔀 phase transition routing (⛔ blocking), gate-0: phase identification & loading and 🧾 proof-of-load requirement (critical).