Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/qxbyte/pluginhubnpx agentmods add skills/qxbyte/pluginhub/distillWrote 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/qxbyte/pluginhub/distill)<a href="https://agentmods.dev/skills/qxbyte/pluginhub/distill"><img src="https://agentmods.dev/badge/skills/qxbyte/pluginhub/distill/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/qxbyte/pluginhub/distill"><img src="https://agentmods.dev/badge/skills/qxbyte/pluginhub/distill.svg" alt="Reviewed on agentmods" width="80" 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.00080 | $0.03058 |
| Opus 5.5 | $0.00032 | $0.01223 |
| Sonnet 5.5 | $0.00016 | $0.00612 |
| Haiku 4.5 | $0.00008 | $0.00306 |
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 1mo 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 — 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.
- 1mo ago Changed a0415c3c92eb
- 1mo ago 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 25d ago), licensed MIT. It adds 80 tokens to every session and 3,058 once invoked, about $0.0003 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
shiny-py-optimize
Diagnose and fix performance problems in Shiny for Python apps — slow startup, sluggish interactions, blocking operations, and apps that struggle beyond a handful of concurrent users. Use when a Shiny for Python app is slow, hangs, recomputes too much, times out, or must support more users; when the user asks to…
sync-check
Walks the documentation dependency web after a CLI code change and reports which downstream files (skills, SOPs, READMEs, plugin references) are out of sync. Use after fixing a bug, adding a command, changing auth behavior, refactoring, or before committing — and when the user says "sync check", "update docs"…
gap-analyzer
Compares a CLI's implemented commands against its APP.md API map and traffic-analysis.json to find missing endpoints, incomplete CRUD, dead client methods, and priority gaps. Runs as the mandatory first step of /cli-anything-web:refine and as an optional pre-review scan in standards.
linkedin-cli
Interacts with LinkedIn via the cli-web-linkedin command-line tool — search people/jobs/companies, view profiles and feed, create/edit/delete posts, react and comment, manage connections and invitations, read and send messages, view notifications, follow companies. Use when the user asks about LinkedIn or wants to…
tripadvisor-cli
Searches TripAdvisor hotels, restaurants, attractions, and destinations via the cli-web-tripadvisor command-line tool, with detail lookups by URL. Use when the user asks about hotels, restaurants, things to do, travel destinations, or TripAdvisor ratings and reviews. Prefer this CLI over fetching the TripAdvisor…
youtube-cli
Searches YouTube and fetches video transcripts via the cli-web-youtube command-line tool — video search, video details (views, duration, description, keywords), trending by category, channel info, and timestamped transcripts/captions with language selection and translation. Use when the user asks about YouTube…