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 skills add zorost/AI-Engineering-Lab --skill fine-tune-readinessgit clone --depth 1 https://github.com/zorost/AI-Engineering-LabWrote 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/zorost/ai-engineering-lab/fine-tune-readiness)<a href="https://agentmods.dev/skills/zorost/ai-engineering-lab/fine-tune-readiness"><img src="https://agentmods.dev/badge/skills/zorost/ai-engineering-lab/fine-tune-readiness/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/zorost/ai-engineering-lab/fine-tune-readiness"><img src="https://agentmods.dev/badge/skills/zorost/ai-engineering-lab/fine-tune-readiness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.01165 |
| Opus 5 | $0.00023 | $0.00583 |
| Sonnet 5 | $0.00009 | $0.00233 |
| Haiku 4.5 | $0.00005 | $0.00117 |
Grade A, and why
fine-tune-readiness 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 13d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fine-Tune Readiness
1 · Purpose
Fine-tuning is the last resort in a ladder of cheaper levers, this skill makes the team climb the ladder in order, and gates the dataset before a single training run.
2 · When to use
- Whenever "we should fine-tune" is proposed.
- Before any SFT/LoRA/DPO run, to gate the dataset.
- When a fine-tuned model underperforms and nobody knows why (usually: the data).
3 · Inputs
- The task spec with metric and gate (
spec-first-ai-feature). - An eval that can score the behavior change (
eval-first-development). - The failure log from the current prompt/RAG system, clustered
(
error-analysis-50).
4 · Procedure
- Climb the ladder in order, recording the score each rung achieves: (a) better prompting → (b) few-shot examples → (c) RAG with the right documents → (d) fine-tuning. Quote the score at each rung; do not skip rungs.
- Name the failure class fine-tuning is meant to fix. Fine-tuning fixes behavioral classes, format, tone, style, domain vocabulary, consistent refusal/compliance patterns. It does not fix missing facts (that is RAG) or weak reasoning (that is a bigger model or decomposition).
- If the failure class is knowledge or freshness, STOP: use RAG. If it is format or tone and rungs a-c are exhausted, proceed.
- Gate the dataset before training:
- ≥ 200 examples for SFT format/behavior shifts (1,000+ for real moves); preference pairs for DPO.
- Every example reviewed or generated against a written standard.
- No PII unless the compliance sign-off exists in writing.
- A held-out slice (≥ 10%) that training never sees.
- Choose the method: LoRA/QLoRA first (small adapter, reversible, cheap); full fine-tune only when adapters demonstrably cannot move the metric. DPO only after SFT, when you have preference pairs.
- Compute the hardware budget (
local-model-fit) or the cloud training cost before launching. Write the number down. - Train, then score on the held-out slice and the golden set. Compare against the best prompt/RAG rung, not against the untrained base model alone.
- Ship only if the fine-tune beats the best non-trained rung by a margin that justifies the serving and maintenance cost. Record the decision and the numbers.
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.
- 13d ago First seen · 96 lines · 46 tokens per session scan A 26bf0256872c
fine-tune-readiness is a skill published in the GitHub repository zorost/AI-Engineering-Lab (303 stars, last pushed 25d ago), licensed MIT. It adds 46 tokens to every session and 1,165 once invoked, about $0.0002 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
ai-engineering-toolkit
6 production-ready AI engineering workflows: prompt evaluation (8-dimension scoring), context budget planning, RAG pipeline design, agent security audit (65-point checklist), eval harness building, and product sense coaching.
llm-ops
LLM Operations -- RAG, embeddings, vector databases, fine-tuning, prompt engineering avancado, custos de LLM, evals de qualidade e arquiteturas de IA para producao.
ai-engineering-toolkit
AI Engineering Toolkit workflow skill. Use this skill when the user needs 6 production-ready AI engineering workflows: prompt evaluation (8-dimension scoring), context budget planning, RAG pipeline design, agent security audit (65-point checklist), eval harness building, and product sense coaching and the operator…
ai-engineering-toolkit
6 production-ready AI engineering workflows: prompt evaluation (8-dimension scoring), context budget planning, RAG pipeline design, agent security audit (65-point checklist), eval harness building, and product sense coaching.
ai-engineering-toolkit
6 production-ready AI engineering workflows: prompt evaluation (8-dimension scoring), context budget planning, RAG pipeline design, agent security audit (65-point checklist), eval harness building, and product sense coaching.
ai-engineering-toolkit
6 production-ready AI engineering workflows: prompt evaluation (8-dimension scoring), context budget planning, RAG pipeline design, agent security audit (65-point checklist), eval harness building, and product sense coaching.