Borrowing it
Nothing to install: this file belongs to nbaradar/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/nbaradar/obsidian-mcp-server/main/AGENTS.mdgit clone --depth 1 https://github.com/nbaradar/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/nbaradar/obsidian-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/nbaradar/obsidian-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/nbaradar/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.05118 | $0.05118 |
| Opus 5 | $0.02559 | $0.02559 |
| Sonnet 5 | $0.01024 | $0.01024 |
| Haiku 4.5 | $0.00512 | $0.00512 |
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 7d 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 — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Obsidian MCP Server — AGENTS.md
Purpose
This document outlines the purpose and structure of the Obsidian MCP Server, which connects Claude Desktop (as an MCP client) to a local Obsidian vault. The server allows the model to perform basic operations on markdown files in a secure, sandboxed environment.
Overview
The goal of the MCP server is to expose the contents of one or more local Obsidian vaults (for example nader_obsidian_vault) as resources that can be read and modified through defined MCP tool calls. This enables local automation, structured note editing, and future integration with other projects or vaults.
The server will:
- Serve as a bridge between Claude Desktop and the local Obsidian vault.
- Expose CRUD functionality for markdown files across approved vaults.
- Operate locally (localhost only) for privacy and security.
- Be extensible for future specialized vaults or tools.
Implementation Plan
The first version will be written in Python, using FastMCP for rapid setup and uv as the package manager. It will not include any prompts yet—only resources (markdown files) and tools (file operations).
Resources (planned)
- Markdown Files: Each
.mdfile in the vault is a resource. - Each resource will have basic metadata such as file path and frontmatter (now surfaced through dedicated tools).
Tools (current)
All MCP tools live in obsidian_vault.py and are simple wrappers over helper functions that enforce our sandbox rules. Every tool now accepts an optional vault argument; omitting it causes the server to use the caller’s per-session active vault (falling back to the config default). Responses always include the resolved vault name so downstream automations have an audit trail.
Management
list_vaults— Returns the default vault, the caller’s active vault (if set), and metadata for each configured vault (name, path, description, existence flag). Primary discovery entry point.set_active_vault— Stores the caller’s preferred vault for the lifetime of the MCP session. Subsequent tool calls without avaultargument use this value.
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.
- 7d ago First seen · 330 lines · 5,118 tokens per session scan A cb2f2cf07683
obsidian-mcp-server AGENTS.md is an instructions file published in the GitHub repository nbaradar/obsidian-mcp-server (1 stars, last pushed 10mo ago), licensed MIT. It adds 5,118 tokens to every session, about $0.0256 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
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.
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).
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.