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/understudylabs/understudy-agent-tools/distill-classifiernpx skills add understudylabs/understudy-agent-tools --skill distill-classifiergit clone --depth 1 https://github.com/understudylabs/understudy-agent-toolsWhat 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.00105 | $0.01549 |
| Opus 5 | $0.00053 | $0.00775 |
| Sonnet 5 | $0.00021 | $0.00310 |
| Haiku 4.5 | $0.00011 | $0.00155 |
Grade A, and why
distill-classifier 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 2d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Distill Classifier
Most production LLM calls are not agents — they are classifiers: tag, route,
score, extract. This worker replaces a frontier classifier with a fine-tuned
open-weight student using teacher-as-labeler hard-label distillation: an
ensemble of teachers votes labels onto unlabeled rows, the student trains on the
consensus, and a gated verdict decides whether it ships. It does not cover
reasoning or tool-calling workloads — for those use
../compare-trajectories/SKILL.md and the
training rungs it feeds.
Decision Gate
Right move when the task is knowledge-bound classification (domain label
boundaries, not instruction-following), call volume justifies a ~$5–15
experiment, and either the teacher's logits are closed (hard labels are all you
can get) or several teachers are available. Wrong move when prompt optimization
hasn't been tried — run ../optimize-workload/SKILL.md
(GEPA) first; it has moved classifiers +8pp accuracy with no weight update, and
SFT is only warranted after it plateaus against a measured baseline.
Safety Gates
- Do not upload source files, prompts, traces, labels, or datasets unless the developer explicitly approves that exact action in the current thread. Teacher-labeling calls send rows to providers — name the row count and get approval before the sweep.
- Frozen splits before any labeling: train/dev/holdout from
../capture-evidence/SKILL.md, with a leakage check across splits. Teachers label train only; dev is for checkpoints; holdout is scored once, at the end. - Never report accuracy on imbalanced classes — macro-F1 and per-class recall are the promotion metrics; accuracy hides class collapse.
- Run the confound ablations (see
reference.md) before attributing any lift to training.
Flow
- Baseline the teachers. Score ≥2 (prefer 3) frontier/strong models on a
balanced labeled sample (≥200 rows/class). Record per-model macro-F1 and
per-class recall. Pick the N best teachers — mean teacher quality
predicts student quality; teacher diversity does not (confirmed null, see
reference.md). - Try the no-weight rung. GEPA on train rows only. If macro-F1 lands within ~3pp of the best-teacher ceiling, stop — ship the prompt.
- Consensus-label train. Each teacher labels every train row; majority vote per row (per label for multi-label). Keep ≥80% of rows: volume beats purity — strict confidence filtering measurably hurts (−8pp macro-F1 in the controlled comparison). Set the split-vote rows aside as the disagreement set.
- Build a failure-directed corpus. Run the student zero-shot on train; build the SFT set as roughly 60–70% student-miss rows (consensus label the student got wrong) plus 30–40% unanimous correct rows balancing the minority class to ~50/50. Targeting residual failures beats a larger clean-unanimous corpus.
- LoRA SFT. One epoch, conservative LR, and LoRA rank ≥64 — r32 and
below cannot override the base model's class prior and collapses minority
recall (the single most load-bearing hyperparameter measured; details in
reference.md). Train locally via../local-distillation-lab/SKILL.mdor export the JSONL for a hosted SFT job (approval-gated; size it with../plan-hosted-run/SKILL.md). - Validate, then verdict. On dev: macro-F1 vs best teacher, per-class
recall ≥50% everywhere, schema-validity 100% for structured output. Then
one holdout pass and a four-way verdict:
- PROMOTE — beats the bar at ≤ the cost target → route it
(
../use-understudy-gateway/SKILL.md). - SHADOW-TEST — passes overall but a critical class is marginal.
- COLLECT-MORE-DATA — holdout too thin (<~120 rows) to decide.
- STOP — far below bar after GEPA and SFT; do not iterate hyperparameters more than twice — the ceiling is the data or the task.
- PROMOTE — beats the bar at ≤ the cost target → route it
(
- Escalation (optional). If the student plateaus exactly on the
disagreement set and an open teacher with logits is available, soft-target
distillation on that boundary slice is the next rung (measured +7.9pp on
ambiguous classes; see
reference.md).
What ships with it
1 file 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.
- 2d ago First seen · 111 lines · 105 tokens per session scan A bd7c8a472d43
distill-classifier is a skill published in the GitHub repository understudylabs/understudy-agent-tools (16 stars, last pushed 3d ago), licensed MIT. It adds 105 tokens to every session and 1,549 once invoked, about $0.0005 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-30.
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.