Borrowing it
Nothing to install: this file belongs to rex/mcp-apple-obsidian. 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/rex/mcp-apple-obsidian/main/AGENTS.mdgit clone --depth 1 https://github.com/rex/mcp-apple-obsidianWrote 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/rex/mcp-apple-obsidian/agents-md)<a href="https://agentmods.dev/instructions/rex/mcp-apple-obsidian/agents-md"><img src="https://agentmods.dev/badge/instructions/rex/mcp-apple-obsidian/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.01638 | $0.01638 |
| Opus 5 | $0.00819 | $0.00819 |
| Sonnet 5 | $0.00328 | $0.00328 |
| Haiku 4.5 | $0.00164 | $0.00164 |
Grade A, and why
mcp-apple-obsidian 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 6d 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Apple Obsidian - Agent Guide
Project Overview
This is a comprehensive MCP server for Obsidian on macOS that provides:
- File system access to vaults and notes
- AppleScript integration for app control
- URI scheme support for native Obsidian actions
- Frontmatter/properties CRUD operations
- Tag management across notes and vaults
- Task management with Obsidian-compatible syntax
Architecture
src/mcp_apple_obsidian/
├── __init__.py # Package entry point
├── server.py # FastMCP server with 42 tools
├── config.py # Configuration management
├── applescript.py # AppleScript interface
├── uri_handler.py # Obsidian URI scheme handler
└── vault_fs.py # File system operations for vaults
# + Frontmatter/Tag/Task operations
Key Design Principles
- Three-Layer Access: Always prefer file system > AppleScript > URI for reliability
- Backup Safety: All write operations support automatic backups
- Async Everything: All I/O operations are async for performance
- Graceful Degradation: Works even when Obsidian isn't running
- No stdout pollution: Use stderr for logging (critical for stdio transport)
- YAML-aware: Frontmatter uses YAML for type preservation
- Tag Flexibility: Supports both inline (#tag) and frontmatter tags
- Task Compatibility: Tasks use Obsidian-compatible syntax
Adding New Tools
When adding tools to server.py:
- Import any needed modules at the top
- Use
@mcp.tool()decorator - Use descriptive docstrings (these become tool descriptions)
- Return strings (preferably JSON for structured data)
- Catch exceptions and return error messages
- Log errors to stderr
Example:
@mcp.tool()
async def my_new_tool(vault: str, param: str) -> str:
"""Clear description of what the tool does.
Args:
vault: Name or path of the vault
param: Description of parameter
Returns:
Description of return value
"""
try:
result = await do_something(vault, param)
return json.dumps(result, indent=2)
except Exception as e:
logger.error(f"Error in my_new_tool: {e}")
return f"Error: {e}"
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.
- 6d ago First seen · 232 lines · 1,638 tokens per session scan A 1a272b6ac942
mcp-apple-obsidian AGENTS.md is an instructions file published in the GitHub repository rex/mcp-apple-obsidian (1 stars, last pushed 5mo ago), licensed MIT. It adds 1,638 tokens to every session, about $0.0082 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.