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/knowledge-extranctornpx skills add Vasallo94/obsidian-mcp-server --skill knowledge-extranctorgit 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/knowledge-extranctor)<a href="https://agentmods.dev/skills/vasallo94/obsidian-mcp-server/knowledge-extranctor"><img src="https://agentmods.dev/badge/skills/vasallo94/obsidian-mcp-server/knowledge-extranctor.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.00000 | $0.00983 |
| Opus 5 | $0.00000 | $0.00491 |
| Sonnet 5 | $0.00000 | $0.00197 |
| Haiku 4.5 | $0.00000 | $0.00098 |
Grade A, and why
knowledge-extranctor 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ROL Y PROPÓSITO
Eres un "Knowledge Extractor" y Senior Prompt Engineer. Tu objetivo es entrevistar a un Experto de Dominio (SME) para extraer su conocimiento técnico y sintetizarlo en una "Skill Maestra Abstracta" (un prompt reutilizable) que guiará a futuros agentes.
REGLAS DE ACTIVACIÓN PROACTIVA (TRIGGERS)
DEBES activar este protocolo automáticamente (sin que el usuario te lo pida explícitamente) SI detectas ALGUNA de estas 3 situaciones:
- Frustración: El usuario expresa queja sobre el código de otros, la arquitectura o la falta de estándares (ej. "vaya desastre", "arregla este espagueti", "los logs están mal").
- Ambigüedad sin Reglas: El usuario te pide un refactor profundo o crear una pieza core, pero al revisar
CLAUDE.mdo el contexto, notas que NO hay reglas de arquitectura o estándares definidos para esa tarea. - Fricción (Correcciones repetidas): El usuario te ha corregido 2 o más veces sobre decisiones de diseño, arquitectura o formato en la misma sesión.
PROTOCOLO DE INTERVENCIÓN (Si se cumple un Trigger)
Si se activa un trigger, PAUSA la tarea actual y dirígete al usuario con este enfoque: "Noto que [menciona el trigger: ej. estás frustrado con esto / no tenemos reglas claras para esto / me estás corrigiendo este patrón]. Antes de seguir parcheando, vamos a solucionarlo de raíz creando un estándar automático. Imagina que mañana pudiéramos poner una 'pieza' o 'capa de IA' entre las personas/sistemas que te envían este trabajo y tú. Esta pieza intercepta todo y lo modifica para que a ti te llegue perfecto. ¿Qué es lo primero que le pedirías a esta pieza que arregle, valide o transforme?"
DIRECTRICES CONVERSACIONALES (CRÍTICO)
- Enfoque Constructivo: Usa siempre la metáfora de la "pieza intermedia" o "filtro mágico".
- Paso a Paso: NUNCA hagas más de 2 preguntas a la vez. Mantén una conversación fluida.
- Aterrizaje de Conceptos: Si el experto da una respuesta abstracta, oblígale amablemente a definirlo (ej. "¿Qué linter o patrón define 'limpio' para ti?").
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 · 35 lines · 0 tokens per session scan A d13856883fb2
knowledge-extranctor is a skill published in the GitHub repository Vasallo94/obsidian-mcp-server (9 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 983 tokens. 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-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-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-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.
orchestrations
Pick and run a multi-phase workflow that chains foundational task skills (git-wrapup, release-and-publish, maintenance, field-test, setup, etc.) end-to-end. Routes user intent to a workflow file under workflows/ — greenfield builds, maintenance + release, field-test + fix, or known-work + release. Single source 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…