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.
git clone --depth 1 https://github.com/rygwdn/obsidian-mcp-pluginWrote 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/rules/rygwdn/obsidian-mcp-plugin/mcp-plugin-architecture)<a href="https://agentmods.dev/rules/rygwdn/obsidian-mcp-plugin/mcp-plugin-architecture"><img src="https://agentmods.dev/badge/rules/rygwdn/obsidian-mcp-plugin/mcp-plugin-architecture.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.00284 | $0.00284 |
| Opus 5 | $0.00142 | $0.00142 |
| Sonnet 5 | $0.00057 | $0.00057 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
mcp-plugin-architecture 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.
What it actually says
MCP Plugin Architecture
This plugin follows a structured architecture for tools and resources:
Tools
- Tools are defined in the tools/ directory
- Each tool follows a registration pattern with name, description, and handler
- Tools should use the logger from tools/logging.ts
- Tools for file access should use VaultFileResource
Resources
- Resources provide standardized access to Obsidian data
- The tools/vault_file_resource.ts provides the foundation for file access
- Resources must be registered with the MCP server
- Resources should handle daily notes through tools/daily_note_utils.ts
Daily Notes Support
- Daily notes follow the special scheme:
daily:///<date>(e.g.,daily:///today,daily:///2024-01-15) - Support aliases: "today", "yesterday", "tomorrow"
Server Implementation
- MCP server uses
StreamableHTTPServerTransportfrom@modelcontextprotocol/sdk - Server is defined in mcp_server.ts
- HTTP endpoint at
/mcphandles JSON-RPC requests with Bearer token authentication
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 · 30 lines · 284 tokens per session scan A bb5719cdcfaf
mcp-plugin-architecture is a cursor rule published in the GitHub repository rygwdn/obsidian-mcp-plugin (11 stars, last pushed 6mo ago), licensed MIT. It adds 284 tokens to every session, about $0.0014 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.