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/qxbyte/pluginhub/distillnpx skills add qxbyte/pluginhub --skill distillgit clone --depth 1 https://github.com/qxbyte/pluginhubWhat 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 | $0.00080 | $0.03042 |
| Opus 5 | $0.00040 | $0.01521 |
| Sonnet 5 | $0.00016 | $0.00608 |
| Haiku 4.5 | $0.00008 | $0.00304 |
Grade A, and why
distill 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 yesterday.
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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
distill — project knowledge-base sedimenter (atomic dual-track)
Host-tool convention 🔧:
AskUserQuestionin this skill means a structured multiple-choice question — named for Claude-family hosts (Claude Code / CodeBuddy) where it's most reliable. On a host without it, use the nearest structured-question tool, or fall back to a plain-text question. The behavior (offer choices, wait for the user) is what matters, not the tool name.
Top-level invariant 🔒
The KB is "for locating, not for facts". Every knowledge point distill writes is a location pointer — file path + call chain + reusable navigation experience, not a factual conclusion. The retrieval side uses it only to quickly locate real code; real code is always the only source of truth. Never advance a new requirement on KB content alone, or treat a historical conclusion as the truth about current code. This invariant is the reason the whole design exists; where any downstream behavior conflicts with it, this rule wins (see design doc §0).
The primary product is the project directory <project_root>/knowledge-base/ (what the retrieval side reads), not Obsidian. Obsidian is only an optional human-readable copy.
Positioning & history
distill is a manual, on-demand sedimenter: it turns a finished (or in-progress) spec + the current agent context into a set of atomic knowledge points (one requirement fans out into N standalone docs), files them into the spec's owning project knowledge-base/, and maintains a lightweight index MEMORY.md.
md-only (produces only markdown, no silent injection). Current shape = a project-knowledge-base/-primary atomic dual-track (case + navigation) location sedimenter + optional Obsidian copy. (The v1-v3 auto-injection / yml shape was fully removed in 4.0.0 / 5.0.1; for the old behavior checkout backup/specode-v3.4.0-task-swarm-v0.9.2. History detail is in the CHANGELOG.)
Trigger
/specode:distill <slug> [--target-dir <abs-path>]
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 162 lines · 80 tokens per session scan A 8d663a0c6b89
distill is a skill published in the GitHub repository qxbyte/pluginhub (3 stars, last pushed 27d ago), licensed MIT. It adds 80 tokens to every session and 3,042 once invoked, about $0.0004 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
douyin-favorites-to-knowledge
将用户已授权账号中的抖音视频收藏或用户明确指定的喜欢列表配置并同步到本地 Markdown 或 Obsidian 知识库；默认收藏，只有用户明确说喜欢/点赞才切换来源。首次明确选择推荐的 SiliconFlow转录、本地 Whisper 或不转录。不得绕过登录、访问他人账号或泄露 Cookie 与私密数据。.
knowledge-extractor
Entrevista a un experto de dominio (SME) para extraer su conocimiento técnico tácito y sintetizarlo en una Skill reutilizable. Se activa PROACTIVAMENTE ante 3 situaciones: (1) Frustración — el usuario se queja de código, arquitectura o falta de estándares; (2) Ambigüedad sin Reglas — se pide un refactor profundo pero…
MCP Developer
Skill para desarrollar, mantener y extender el servidor MCP de Obsidian. Incluye patrones de código, arquitectura, testing y gestión de paquetes.
Python Patterns
Buenas prácticas y patrones de desarrollo Python para el proyecto MCP. Incluye estándares de código, patrones arquitectónicos, y convenciones.
Refactoring
Guía para refactorizar código Python de forma segura y efectiva. Incluye técnicas de refactoring, detección de code smells, y mejoras.
Test Runner
Skill para ejecutar y gestionar tests. Incluye patrones de testing, fixtures comunes, y estrategias de debugging de tests fallidos.