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 bastos/skills --skill review-training-data-qualitygit clone --depth 1 https://github.com/bastos/skillsWrote 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/bastos/skills/review-training-data-quality)<a href="https://agentmods.dev/skills/bastos/skills/review-training-data-quality"><img src="https://agentmods.dev/badge/skills/bastos/skills/review-training-data-quality/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/bastos/skills/review-training-data-quality"><img src="https://agentmods.dev/badge/skills/bastos/skills/review-training-data-quality.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.00050 | $0.00433 |
| Opus 5 | $0.00025 | $0.00217 |
| Sonnet 5 | $0.00010 | $0.00087 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade A, and why
review-training-data-quality 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 9d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Training Data Quality
Test whether the dataset teaches the intended capability rather than merely producing an easy loss curve.
Inspect deterministic distributions
Summarize every product-relevant axis by split and overall: source group, task lane, goal, format, label, abstention, difficulty, candidate count, sequence length, terminal state, role, and preferred-answer position.
Use the generic JSONL summary helper:
python scripts/summarize_jsonl_fields.py corpus.jsonl \
--field split --field lane --field goal --field label \
--output quality-distributions.json
Look beyond equal row counts. Verify group-safe splits, distinct source groups, reasonable joint distributions, and enough examples at safety boundaries. Flag any category whose dominance would let the model ignore important context.
Review candidate and label quality
Check that:
- positives are legal, plausible, and supported by supplied context;
- hard negatives are tempting but wrong for an explainable reason;
- multiple acceptable answers are preserved when evidence supports them;
- abstention is available and labeled only when warranted;
- teacher outputs use supplied identifiers and validate without silent repair;
- prompts exclude reference answers and teacher-only metadata;
- every lane has sufficient facts to make a defensible choice.
Run a small balanced teacher preflight before labeling the full corpus. Stop on identifier, replay, legality, terminal-boundary, context, or label-collapse failures.
Test label defensibility
Blind-review difficult representative cases twice with candidate order reversed. Select cases from metadata, not label outcomes. Count a judgment as stable only when both orders choose the same underlying answer. Preserve ties, ambiguity, both-poor, and insufficient-context results.
Define the stability threshold before review. If the threshold fails, fix the smallest corpus or rubric defect before scaling. More examples of the same biased lane are not evidence of broader capability.
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.
- 9d ago First seen · 43 lines · 50 tokens per session scan A 0ad6d7e0b4f2
review-training-data-quality is a skill published in the GitHub repository bastos/skills (7 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 433 once invoked, about $0.0003 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-31.
Other skills, from other repositories
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…
oracle
Best practices for using the oracle CLI (prompt + file bundling, engines, sessions, and file attachment patterns).
model-usage
Use CodexBar CLI local cost usage to summarize per-model usage for Codex or Claude, including the current (most recent) model or a full model breakdown. Trigger when asked for model-level usage/cost data from codexbar, or when you need a scriptable per-model summary from codexbar cost JSON.
agent-development
Design and build custom Claude Code agents with effective descriptions, tool access patterns, and self-documenting prompts. Covers Task tool delegation, model selection, memory limits, and declarative instruction design. Use when: creating custom agents, designing agent descriptions for auto-delegation…
blockrun
Use when user needs capabilities Claude lacks (image generation, real-time X/Twitter data) or explicitly requests external models ("blockrun", "use grok", "use gpt", "dall-e", "deepseek").
ai-wrapper-product
Expert in building products that wrap AI APIs (OpenAI, Anthropic, etc.) into focused tools people will pay for. Not just 'ChatGPT but different' - products that solve specific problems with AI. Covers prompt engineering for products, cost management, rate limiting, and building defensible AI businesses. Use when: AI…