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 skills/vasallo94/obsidian-mcp-server/mcp-developernpx skills add Vasallo94/obsidian-mcp-server --skill mcp-developergit clone --depth 1 https://github.com/Vasallo94/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/skills/vasallo94/obsidian-mcp-server/mcp-developer)<a href="https://agentmods.dev/skills/vasallo94/obsidian-mcp-server/mcp-developer"><img src="https://agentmods.dev/badge/skills/vasallo94/obsidian-mcp-server/mcp-developer.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.00033 | $0.02369 |
| Opus 5 | $0.00016 | $0.01184 |
| Sonnet 5 | $0.00007 | $0.00474 |
| Haiku 4.5 | $0.00003 | $0.00237 |
Grade A, and why
MCP Developer 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.
How it starts
The opening of the file, as written. The whole thing — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Server Developer
Cuándo usar esta skill
- Cuando añadas nuevas herramientas (tools) o recursos al servidor MCP.
- Cuando resuelvas bugs o mejores el rendimiento del servidor.
- Cuando necesites ejecutar tests o linters en este proyecto.
- Cuando modifiques la configuración o el sistema de logging.
Arquitectura del Proyecto
obsidian-mcp-server/
├── obsidian_mcp/
│ ├── server.py # Punto de entrada - crea FastMCP y registra módulos
│ ├── config.py # Pydantic Settings (OBSIDIAN_VAULT_PATH, LOG_LEVEL)
│ ├── tools/ # Herramientas MCP (funciones invocables)
│ │ ├── navigation.py # Leer, listar, buscar notas
│ │ ├── creation.py # Crear, editar, eliminar notas
│ │ ├── analysis.py # Estadísticas, gestión de tags
│ │ ├── graph.py # Backlinks, notas huérfanas
│ │ ├── agents.py # Cargador de skills (del vault del usuario)
│ │ ├── semantic.py # Integración RAG/búsqueda vectorial
│ │ ├── context.py # Contexto y estructura del vault
│ │ └── youtube.py # Extracción de transcripciones
│ ├── semantic/ # Módulo RAG opcional (ChromaDB)
│ │ ├── indexer.py # Generación de embeddings
│ │ ├── retriever.py # Búsqueda por similitud
│ │ └── service.py # API de alto nivel RAG
│ ├── resources/ # Recursos MCP (endpoints de solo lectura)
│ ├── prompts/ # Prompts MCP (system prompts para IA)
│ └── utils/ # Utilidades compartidas
│ ├── logging.py # Logging centralizado (a stderr)
│ ├── security.py # Validación de rutas
│ └── vault.py # Operaciones de archivos del vault
├── tests/ # Suite de tests pytest
└── docs/ # Documentación
Reglas Core (Estrictas)
Package Management
- SIEMPRE usa
uv. NUNCA uses pip. - Instalar:
uv add package - Ejecutar:
uv run tool - Dev dependencies:
uv add --dev package
Type Hints
- Requeridos al 100% en todo el código.
- Verificar con:
uv run pyright
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 · 336 lines · 33 tokens per session scan A 5172fe2fcaa4
MCP Developer is a skill published in the GitHub repository Vasallo94/obsidian-mcp-server (9 stars, last pushed 3d ago), licensed MIT. It adds 33 tokens to every session and 2,369 once invoked, about $0.0002 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 skills, from other repositories
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
add-tool
Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.
api-linter
MCP definition linter rules reference. Use when bun run lint:mcp or bun run devcheck reports a lint error or warning (format-parity, schema-is-object, name-format, server-json-, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.