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/5queezer/distill/releasenpx skills add 5queezer/distill --skill releasegit clone --depth 1 https://github.com/5queezer/distillWhat 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.00000 | $0.00821 |
| Opus 5 | $0.00000 | $0.00411 |
| Sonnet 5 | $0.00000 | $0.00164 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
release 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release to PyPI
Bump version, tag, and publish to PyPI via the existing GitHub Actions workflow.
Arguments
<version>— explicit version (e.g.0.4.0). Optional.major/minor/patch— bump type. Optional.- No argument — auto-detect from conventional commits since last tag.
Workflow
1. Determine version
If no explicit version given, auto-detect from commit history:
# Find last tag
LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
# Get commits since last tag (or all commits if no tag)
if [ -n "$LAST_TAG" ]; then
COMMITS=$(git log "$LAST_TAG"..HEAD --oneline)
else
COMMITS=$(git log --oneline)
fi
Scan commit messages for the highest bump level:
| Pattern | Bump |
|---|---|
feat!: or BREAKING CHANGE: in body |
MAJOR |
feat: or feat(scope): |
MINOR |
fix:, perf:, ref:, docs:, chore:, build:, ci:, test:, style: |
PATCH |
Rules:
- Use the highest bump found (MAJOR > MINOR > PATCH)
- If no conventional commits found, default to PATCH
- Parse current version from
pyproject.toml:grep '^version' pyproject.toml - Calculate new version by incrementing the appropriate component (reset lower components to 0)
Show the user: commit summary, detected bump level, and proposed version. Wait for confirmation before proceeding.
2. Validate
- Confirm on
mainbranch:git branch --show-current - Confirm working tree is clean:
git status --short(ignore.claude/settings.json) - Confirm the tag
v<version>does not already exist:git tag -l v<version> - Confirm CI is green on main:
gh run list --branch main --workflow ci.yml --limit 1 --json conclusion --jq '.[0].conclusion'
If any check fails, stop and explain why.
3. Bump version
Update the version string in two files:
# pyproject.toml — version = "X.Y.Z"
# src/distill_mcp/__init__.py — __version__ = "X.Y.Z"
Use the Edit tool (not sed) to replace the old version with the new one.
4. Commit and tag
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 · 103 lines · 0 tokens per session scan A c212e6c493fd
release is a skill published in the GitHub repository 5queezer/distill (1 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 821 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.