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/frstlvl/obsidian-mcp-server/agents-mdgit clone --depth 1 https://github.com/frstlvl/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/frstlvl/obsidian-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/frstlvl/obsidian-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/frstlvl/obsidian-mcp-server/agents-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.05196 | $0.05196 |
| Opus 5 | $0.02598 | $0.02598 |
| Sonnet 5 | $0.01039 | $0.01039 |
| Haiku 4.5 | $0.00520 | $0.00520 |
Grade A, and why
obsidian-mcp-server 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 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.
This is a copy
89% identical to obsidian-mcp-server copilot-instructions.md — 125 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 754 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Obsidian MCP Server - AI Instructions
Project Overview
This is a Model Context Protocol (MCP) server that provides real-time Claude AI access to Obsidian vaults. The server enables dynamic querying, searching, and reading of notes without token limitations through JSON-RPC 2.0 over stdio.
Key Purpose: Bridge Claude AI with Obsidian knowledge bases through efficient, secure, real-time vault access.
Issue Tracking
This project uses bd (beads) for issue tracking.
Run bd prime for workflow context, or install hooks (bd hooks install) for auto-injection.
Quick reference:
bd ready- Find unblocked workbd create "Title" --description "Description" --type task --priority 2- Create issuebd close <id>- Complete workbd sync- Sync with git (run at session end)
For full workflow details: bd prime
Critical Project Context
MCP Architecture (CRITICAL)
- Protocol: JSON-RPC 2.0 over stdio (stdin/stdout), NOT REST/HTTP
- Server Model: Long-running process with structured message communication
- Resources: Vault notes exposed as
obsidian://vault/[path]URIs - Tools: Functions callable by Claude (list_vaults, search_vault, create_note, etc.)
- Multi-Vault: Single server instance serving multiple vaults via
vaultsconfig array - Implementation: TypeScript using @modelcontextprotocol/sdk
Technology Stack
Runtime & Build:
- Node.js 18+ (recommended 20+)
- TypeScript 5.7+ with strict mode
- ES Modules (type: "module" in package.json)
Core Dependencies:
@modelcontextprotocol/sdk- MCP protocol implementation@xenova/transformers- Local embedding generation (Transformers.js)vectra- Local vector database for semantic searchchokidar- File system watcher for automatic index updateswinston- Structured logging systemgray-matter- YAML frontmatter parsingzod- Runtime type validation
Development:
tsx- TypeScript execution and hot reloadprettier- Code formattingeslint- Code linting
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 · 754 lines · 5,196 tokens per session scan A c7b4b9077d3f
obsidian-mcp-server AGENTS.md is an instructions file published in the GitHub repository frstlvl/obsidian-mcp-server (1 stars, last pushed 4mo ago), licensed MIT. It adds 5,196 tokens to every session, about $0.0260 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to obsidian-mcp-server copilot-instructions.md, differing in 125 lines, and is treated as a copy.
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).
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.
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.
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 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).