Borrowing it
Nothing to install: this file belongs to smith-and-web/obsidian-mcp-server. 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/smith-and-web/obsidian-mcp-server/main/CLAUDE.mdgit clone --depth 1 https://github.com/smith-and-web/obsidian-mcp-serverWrote 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/smith-and-web/obsidian-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/smith-and-web/obsidian-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/smith-and-web/obsidian-mcp-server/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.1 | $0.00947 | $0.00947 |
| Opus 5 | $0.00474 | $0.00474 |
| Sonnet 5 | $0.00189 | $0.00189 |
| Haiku 4.5 | $0.00095 | $0.00095 |
Grade A, and why
obsidian-mcp-server 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 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Obsidian MCP Server — Project Conventions
A Model Context Protocol server that lets AI assistants interact with an Obsidian vault (notes, frontmatter, tags, search, links) over an SSE transport.
Stack
- Language: TypeScript 5.x, ES modules (
"type": "module"). Useimport/export, neverrequire. - Runtime: Node.js >= 20.19. Build target is
dist/viatsc. - HTTP: Express 5.
- MCP:
@modelcontextprotocol/sdk. - Frontmatter:
gray-matter. - Tests: Vitest. Lint: ESLint + Prettier (Prettier rules are enforced through ESLint).
Commands
| Task | Command |
|---|---|
| Install | npm install |
| Build | npm run build (tsc → dist/) |
| Dev server (watch) | npm run dev |
| Test | npm test (vitest run) |
| Test (watch) | npm run test:watch |
| Lint | npm run lint (eslint src/) |
| Auto-fix lint/format | npm run lint:fix then npm run format |
| Format check | npm run format:check |
Always run npm test and npm run lint before opening a PR — both must pass clean.
Prettier violations surface as ESLint errors, so npm run lint:fix resolves most formatting issues.
Layout
src/
├── index.ts # Express server entrypoint & wiring
├── server/
│ ├── mcp.ts # MCP protocol handling (SSE connection, message routing)
│ └── middleware.ts # Express middleware (auth, etc.)
├── tools/
│ ├── definitions.ts # Tool schemas (JSON Schema inputSchema)
│ ├── handlers.ts # Tool execution → dispatches to VaultManager
│ └── index.ts # Re-exports
├── vault/
│ ├── VaultManager.ts # Core vault operations (the real logic lives here)
│ └── frontmatter.ts # YAML frontmatter utilities (gray-matter)
└── types/
└── index.ts # Shared types
tests/ # Vitest specs (*.test.js) — mirror the src module under test
examples/test-vault/ # Sample vault used by examples and manual testing
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 · 86 lines · 947 tokens per session scan A 557962de286f
obsidian-mcp-server CLAUDE.md is an instructions file published in the GitHub repository smith-and-web/obsidian-mcp-server (18 stars, last pushed today), licensed MIT. It adds 947 tokens to every session, about $0.0047 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.