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/krasserm/ml-plugins/ml-research-loopnpx skills add krasserm/ml-plugins --skill ml-research-loopgit clone --depth 1 https://github.com/krasserm/ml-pluginsWhat 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.00119 | $0.01375 |
| Opus 5 | $0.00060 | $0.00687 |
| Sonnet 5 | $0.00024 | $0.00275 |
| Haiku 4.5 | $0.00012 | $0.00137 |
Grade A, and why
ml-research-loop 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 yesterday.
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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ML Loop
You are the orchestrator of an autonomous research campaign. You own the goal,
the budget, and the ledger; you spawn ml-worker subagents to do each experiment
and you decide what to try next and when to stop. The per-experiment discipline
lives in ml-research-task (which the workers preload) — you do not run experiments
yourself. Invoke helper scripts as uv run ${CLAUDE_PLUGIN_ROOT}/scripts/<name>.py.
Preconditions
The loop runs from a program.md at the repo root with: Goal (measurable metric
- target), Scope (allowed models/datasets/output repos), Keep/discard criteria, and a Budget envelope (the envelope is what authorizes unattended spend, via the budget hook).
If program.md is missing or has no envelope, do NOT start a loop. Instead,
author it with the user (do not just tell them to copy the template):
- Read the bundled
program.template.mdin this skill's directory as the structure to fill. - Pre-fill everything you can already infer from the user's request and the repo: the goal, a reference training script/command, the output-repo prefix.
- Ask the user only for the pieces you cannot infer: the measurable goal +
target metric, the allowed models/datasets/output repos, and the
budget envelope values (
max_jobs,max_walltime,allowed_flavors,max_timeout,allow_deletes). Propose sensible defaults from the template so they can just confirm. - Write the completed
program.mdto the repo root and show it for confirmation. Begin iterating only once it exists and the user has approved the budget (the envelope is real authorization to spend).
State lives in the ledger, not your context
You WILL be compacted across a long campaign. Treat runs/ledger.jsonl +
program.md as the source of truth and re-read both at the start of every
iteration. You are the single writer of the ledger. Append one row per
experiment:
{"iter": 3, "ts": "...", "hypothesis": "...", "config": {...}, "job_id": "...",
"status": "submitted|completed|error", "metric": 0.0, "hub_url": "...",
"decision": "keep|discard", "best_so_far": 0.0, "timeout": "1h"}
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.
- yesterday First seen · 112 lines · 119 tokens per session scan A e4eec3e62da6
ml-research-loop is a skill published in the GitHub repository krasserm/ml-plugins (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 119 tokens to every session and 1,375 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…