Borrowing it
Nothing to install: this file belongs to tboome33/obsidian-mcp-router. 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/tboome33/obsidian-mcp-router/main/AGENTS.mdgit clone --depth 1 https://github.com/tboome33/obsidian-mcp-routerWrote 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/tboome33/obsidian-mcp-router/agents-md)<a href="https://agentmods.dev/instructions/tboome33/obsidian-mcp-router/agents-md"><img src="https://agentmods.dev/badge/instructions/tboome33/obsidian-mcp-router/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/tboome33/obsidian-mcp-router/agents-md"><img src="https://agentmods.dev/badge/instructions/tboome33/obsidian-mcp-router/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.02494 | $0.02494 |
| Opus 5.5 | $0.00998 | $0.00998 |
| Sonnet 5.5 | $0.00499 | $0.00499 |
| Haiku 4.5 | $0.00249 | $0.00249 |
Grade A, and why
obsidian-mcp-router 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 4d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — operating contract for obsidian-mcp-router
Host-neutral instructions for any coding agent working in this repository. Codex, Gemini CLI,
Cursor and Windsurf are all documented as reading this file; per-host provenance — which paths
were confirmed and which are taken on a vendor's word — is recorded in
contracts/agent-host-targets.json. Nothing here assumes a particular harness.
This file is read automatically and will steer actions. Treat it as code: every backticked
repository path and every npm run script below is resolved against the filesystem and against
package.json by tests/agents-md-contract.test.mjs, which fails the suite when one goes stale.
That check does not cover prose, so the rule stands for the rest: do not add a claim here you
have not run.
What this repository is
An MCP server that routes tool calls to one or more Obsidian vaults over each vault's Local REST
API, packaged together with the skills, slash commands, agents and hooks that drive it. Node
>=20.19.0, ESM only ("type": "module"), no build step — the source in src/ is what runs.
Layout, all paths relative to the repository root:
| Path | What lives there |
|---|---|
bin/ |
CLI entry point for the MCP server |
src/ |
Server, tool implementations, helpers |
scripts/ |
Operational CLIs (setup, validation, gates, release) |
skills/ |
The know-how pages — one directory per skill, each with a SKILL.md |
commands/ |
Slash-command definitions |
agents/ |
Sub-agent definitions |
hooks/ |
Session hooks |
contracts/ |
Machine-checked declarations (see below) |
templates/ |
Files copied into vaults during setup |
tests/ |
node:test suites |
docs/ |
Long-form documentation |
view-agent/ |
The view-link provider (stdlib Python, its own unittest suite: npm run test:view-agent) — a separate service deployed on the host where the Obsidian GUIs run, not part of the plugin's runtime |
The three gates
Run all three before claiming anything is finished. They are independent and catch different failures.
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.
- 4d ago Changed · +1 lines · +55 tokens per session 03615eca759e
- 1mo ago Changed 60f8fb973850
- 1mo ago First seen · 191 lines · 2,439 tokens per session scan A e674a503a6e0
obsidian-mcp-router AGENTS.md is an instructions file published in the GitHub repository tboome33/obsidian-mcp-router (1 stars, last pushed today), licensed Apache-2.0. It adds 2,494 tokens to every session, about $0.0100 per session on Opus 5.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
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, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.