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/lawwu/agentic-ml-plugin/check-data-pipelinenpx skills add lawwu/agentic-ml-plugin --skill check-data-pipelinegit clone --depth 1 https://github.com/lawwu/agentic-ml-pluginWrote 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/lawwu/agentic-ml-plugin/check-data-pipeline)<a href="https://agentmods.dev/skills/lawwu/agentic-ml-plugin/check-data-pipeline"><img src="https://agentmods.dev/badge/skills/lawwu/agentic-ml-plugin/check-data-pipeline.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.1 | $0.00122 | $0.02056 |
| Opus 5 | $0.00061 | $0.01028 |
| Sonnet 5 | $0.00024 | $0.00411 |
| Haiku 4.5 | $0.00012 | $0.00206 |
Grade A, and why
check-data-pipeline 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 5d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 5d ago First seen · 216 lines · 122 tokens per session scan A b2613bc51677
check-data-pipeline is a skill published in the GitHub repository lawwu/agentic-ml-plugin (3 stars, last pushed 5mo ago), with no licence file. It adds 122 tokens to every session and 2,056 once invoked, about $0.0006 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
ds-validate
Chooses a leakage-safe way to split data — temporal, grouped, stratified, or nested cross-validation — matched to how the rows are actually structured, and decided before any model is trained. Use when someone asks how to split into train and test, set up cross-validation, or pick between KFold, GroupKFold…
langchain-context
Answers questions about the LangChain Python ecosystem — the langchain-ai/langchain monorepo (langchain-core, v1 agents, langchain-classic, in-tree partners, text-splitters) plus companion repos LangGraph, LangSmith SDK, Deep Agents, out-of-tree partner monorepos langchain-google and langchain-aws, and the…
meta-prompt-optimizer
Audit and rewrite prompts against Claude Opus 4.7 instruction-following best practices. Produces a scored audit plus a rewritten prompt. Use when the user asks to audit, review, critique, rewrite, improve, optimize, tighten, score, fix, migrate, or draft a prompt — including system prompts, CLAUDE.md files, Claude…
uncertainty-quantification
Reports every score with its spread across folds or seeds, and says whether a gap between two numbers is bigger than that spread. Use when someone asks whether an improvement is real or just noise, or how confident to be that one model beats another. Use when two results are being called different or the same without…
ds-iterate
Reads the evaluation's findings, names what is actually wrong — bias, variance, a weak slice, suspected leakage, a data problem — and routes back to the stage that fixes it. Use when a result is not good enough and someone asks what to try next. Use when deciding whether to go back and change features, change the…
ds-report
Turns evaluation and interpretation into a stakeholder-facing narrative — recommendation, assumptions, and limitations stated plainly. Use when someone asks to write up, summarise, or present results. Use when preparing findings for a product team, a manager, or any audience that will act on them.