Borrowing it
Nothing to install: this file belongs to Vasallo94/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/Vasallo94/obsidian-mcp-server/main/.agents/skills/docs-updater/SKILL.mdgit 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/docs-updater)<a href="https://agentmods.dev/skills/vasallo94/obsidian-mcp-server/docs-updater"><img src="https://agentmods.dev/badge/skills/vasallo94/obsidian-mcp-server/docs-updater/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/skills/vasallo94/obsidian-mcp-server/docs-updater"><img src="https://agentmods.dev/badge/skills/vasallo94/obsidian-mcp-server/docs-updater.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.00874 |
| Opus 5.5 | $0.00012 | $0.00350 |
| Sonnet 5.5 | $0.00006 | $0.00175 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
Documentation Updater 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 2mo 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Updater Skill
Cuándo usar esta skill
- Cuando añadas nuevas herramientas (tools) al MCP.
- Cuando modifiques parámetros o comportamiento de herramientas.
- Cuando añadas nuevas features al proyecto.
- Cuando actualices la arquitectura.
Estructura de Documentación
docs/
├── architecture.md # Visión general arquitectónica
├── configuration.md # Variables de entorno y configuración
├── tool-reference.md # Referencia de todas las herramientas MCP
├── semantic-search.md # Guía de búsqueda semántica
├── agent-folder-setup.md # Configuración de carpeta .agents
├── FUTURE.md # Ideas para desarrollo futuro
└── examples/ # Ejemplos de configuración
Documentos a Actualizar por Tipo de Cambio
Nueva herramienta MCP
-
docs/tool-reference.md- Añadir entrada con:- Nombre de la herramienta
- Descripción
- Parámetros (nombre, tipo, requerido, descripción)
- Ejemplo de uso
- Valor de retorno
-
CHANGELOG.md- Añadir en[Unreleased] > Added
Cambio en configuración
docs/configuration.md- Actualizar tabla de variablesREADME.md- Si afecta quickstart
Cambio arquitectónico
docs/architecture.md- Actualizar diagramas y descripcionesCHANGELOG.md- Documentar en Changed
Formato para Tool Reference
### nombre_herramienta
**Descripción**: Qué hace la herramienta.
**Parámetros**:
| Nombre | Tipo | Requerido | Descripción |
|--------|------|-----------|-------------|
| param1 | str | Sí | Descripción del parámetro |
| param2 | bool | No | Descripción (default: False) |
**Retorna**: Descripción del valor de retorno.
**Ejemplo**:
```python
result = nombre_herramienta(param1="valor")
## Checklist de Documentación
Al añadir nueva feature:
- [ ] Docstring en el código fuente
- [ ] Entrada en `tool-reference.md` (si es tool)
- [ ] Entrada en `CHANGELOG.md`
- [ ] Actualizar `README.md` si afecta uso básico
- [ ] Actualizar `configuration.md` si añade variables
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.
- 2mo ago First seen · 136 lines · 29 tokens per session scan A 5786272e2438
Documentation Updater is a skill published in the GitHub repository Vasallo94/obsidian-mcp-server (11 stars, last pushed 5d ago), licensed MIT. It adds 29 tokens to every session and 874 once invoked, about $0.0001 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 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.
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-telemetry
Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
polish-docs-meta
Finalize documentation and project metadata for a ship-ready MCP server. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
maintenance
Investigate, adopt, and verify dependency updates — with special handling for @cyanheads/mcp-ts-core. Captures what changed, understands why, cross-references against the codebase, adopts framework improvements, syncs project skills, and runs final checks. Supports two entry modes: run the full flow end-to-end, or…