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/awslabs/agent-plugins/finetuning-techniquenpx skills add awslabs/agent-plugins --skill finetuning-techniquegit clone --depth 1 https://github.com/awslabs/agent-pluginsWrote 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/awslabs/agent-plugins/finetuning-technique)<a href="https://agentmods.dev/skills/awslabs/agent-plugins/finetuning-technique"><img src="https://agentmods.dev/badge/skills/awslabs/agent-plugins/finetuning-technique.svg" alt="Measured on agentmods" 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 | $0.00087 | $0.00558 |
| Opus 5 | $0.00044 | $0.00279 |
| Sonnet 5 | $0.00017 | $0.00112 |
| Haiku 4.5 | $0.00009 | $0.00056 |
Grade A, and why
finetuning-technique 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 4d 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.
What it actually says
Finetuning Technique
Guides the user through selecting a fine-tuning technique based on their use case and validates compatibility with the selected model.
When to Use
- User has decided to finetune and needs to choose a technique
- User wants to change their finetuning technique
- Technique needs to be validated against a selected model
Prerequisites
- A base model has been selected (via model-selection skill). The model name and hub must be known.
- A
use_case_spec.mdfile exists. If not, activate the use-case-specification skill to generate it first.
Workflow
Step 1: Determine Finetuning Technique
Consult references/finetune_technique_selection_guide.md to recommend the best-fit technique based on the use case and the user's needs (SFT, DPO, RLVR, RLAIF).
Present the recommendation and reasoning to the user. Ask if they'd like to go with the recommendation or prefer a different technique.
Step 2: Validate Technique Availability
- Once the user confirms a technique, retrieve the finetuning techniques available for the selected model by running:
python finetuning-technique/scripts/get_recipes.py <model-name> <hub-name>- This returns only the techniques the model actually supports, filtered to SFT, DPO, RLVR, and RLAIF. Only these four techniques are supported — ignore any other techniques even if the model's recipes include them.
- If the chosen technique is available for the model, proceed to Step 3.
- If the chosen technique is not available for the model, explain that the selected model does not support it on SageMaker and offer to go back to model-selection to pick a different model that supports the chosen technique.
Step 3: Confirm Selections
Present a summary to the user:
Here's what we've selected:
- Base model: [model name]
- Fine-tuning technique: [SFT/DPO/RLVR/RLAIF]
References
references/finetune_technique_selection_guide.md— Technique guidance (SFT/DPO/RLVR/RLAIF)
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.
- 4d ago First seen · 51 lines · 87 tokens per session scan A 6489b2a51eda
finetuning-technique is a skill published in the GitHub repository awslabs/agent-plugins (876 stars, last pushed 7d ago), licensed Apache-2.0. It adds 87 tokens to every session and 558 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-30.
Other skills, from other repositories
llm-evaluation
LLM evaluation and testing patterns including prompt testing, hallucination detection, benchmark creation, and quality metrics. Use when testing LLM applications, validating prompt quality, implementing systematic evaluation, or measuring LLM performance.
rag-implementation
Comprehensive guide to implementing RAG systems including vector database selection, chunking strategies, embedding models, and retrieval optimization. Use when building RAG systems, implementing semantic search, optimizing retrieval quality, or debugging RAG performance issues.
huggingface-transformers
Hugging Face Transformers best practices including model loading, tokenization, fine-tuning workflows, and inference optimization. Use when working with transformer models, fine-tuning LLMs, implementing NLP tasks, or optimizing transformer inference.
agentproto-llm-endpoint
Use the local LLM endpoint proxy (localhost:18090) — or your own gated public deployment — to route Claude Code / Claude SDK through custom providers (OpenRouter, Moonshot, Groq, ZAI) via an Anthropic-compatible gateway. Covers adapter-specific behaviors, auth patterns, proxy codenames, and common failure modes.
langfuse-observability
LLM observability with Langfuse — tracing, evaluation, prompt versioning, cost tracking, and LLM-as-judge scoring.
pgvector-search
(Aspirational) Production hybrid search with PGVector + BM25 using Reciprocal Rank Fusion, metadata filtering, and performance optimization for semantic retrieval.