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/droodotfoo/vault-tree/claude-mdgit clone --depth 1 https://github.com/DROOdotFOO/vault-treeWhat 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.00601 | $0.00601 |
| Opus 5 | $0.00300 | $0.00300 |
| Sonnet 5 | $0.00120 | $0.00120 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
vault-tree 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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 75 lines · 601 tokens per session scan A 79effeacd5b1
vault-tree CLAUDE.md is an instructions file published in the GitHub repository DROOdotFOO/vault-tree (2 stars, last pushed 6mo ago), with no licence file. It adds 601 tokens to every session, about $0.0030 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
obsidian-vault-mcp CLAUDE.md
Instructions for ebullient/obsidian-vault-mcp, covering obsidian vault mcp, code style and qa.
obsidian-multivault-mcp AGENTS.md
Instructions for bepitulaz/obsidian-multivault-mcp, covering agents.md — deploying this mcp server on the vps, vps facts (example — change to match yours), gather before you start, do (high level — exact commands in deploy.md) and definition of done (verify — do not assume).
obsidian-multivault-mcp CLAUDE.md
Instructions for bepitulaz/obsidian-multivault-mcp: See AGENTS.md for the deployment brief, and DEPLOY.md for the full step-by-step VPS runbook.
mcp-markdown-vault CLAUDE.md
Instructions for wirux/mcp-markdown-vault, covering claude.md, project overview, development commands, install dependencies and build (compiles to dist/, excludes test files).
ObsidianMCPServer CLAUDE.md
Instructions for otaviocc/ObsidianMCPServer, covering claude.md, common development commands, building and testing, installation options and runtime configuration.
personal-notes-assistant CLAUDE.md
Instructions for coeusyk/personal-notes-assistant, covering personal-notes-assistant, architecture, adding a tool, milvus notes (non-obvious, bit people twice already) and running / testing locally.