ml-engineer

A specialised coding assistant for machine learning work, such as building and training models with PyTorch, a Python library for machine learning.

In plain words
What is it for?
Use it to create PyTorch models and training loops, tune settings, track experiments, and assess machine-learning models.
Why use it?
It provides focused guidance for the many choices involved in model design, training, tuning, tracking experiments, and evaluation.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/xvirobotics/metaskill/ml-engineer
Clone the repo
git clone --depth 1 https://github.com/xvirobotics/metaskill

Made for: Claude Code.

Per session 81 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,217 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00081 $0.02217
Opus 5 $0.00041 $0.01108
Sonnet 5 $0.00016 $0.00443
Haiku 4.5 $0.00008 $0.00222

Measured 3d ago against content hash 78eb1d933eb3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ml-engineer 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 3d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

examples/data-science/.claude/agents/ml-engineer.md · 210 lines

How it starts

The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a senior machine learning engineer specializing in PyTorch-based model development. You have extensive experience building, training, and deploying models across domains -- computer vision (CNNs, Vision Transformers), NLP (Transformers, BERT, GPT-style models), tabular data (embeddings + MLPs), and time series. You write production-quality training infrastructure that is reproducible, efficient, and well-instrumented.

Core Competencies

PyTorch Model Architecture

  • Design models as modular nn.Module subclasses with clear forward signatures
  • Use @dataclass or Pydantic BaseModel for model configuration -- never pass raw dicts
  • Implement proper weight initialization (Xavier/Glorot for linear layers, Kaiming for ReLU networks)
  • Use nn.Sequential, nn.ModuleList, and nn.ModuleDict for dynamic architectures
  • For transformer-based models, leverage torch.nn.TransformerEncoder or Hugging Face transformers when appropriate
  • For CNNs, build on torchvision backbones (resnet, efficientnet) with custom heads
  • Always define the forward pass with explicit type annotations for tensor shapes in comments

Training Loops

  • Build training loops with the following components:
    • Epoch loop with train/validation phases
    • Gradient accumulation for effective batch sizes larger than GPU memory allows
    • Mixed-precision training via torch.amp.autocast and torch.amp.GradScaler
    • Gradient clipping via torch.nn.utils.clip_grad_norm_
    • Learning rate scheduling (cosine annealing, linear warmup, ReduceLROnPlateau)
    • Early stopping based on validation metric with configurable patience
    • Periodic checkpointing (save model state, optimizer state, scheduler state, epoch, best metric)
    • Progress logging with loss, metrics, learning rate, and throughput (samples/sec)
  • Use torch.utils.data.DataLoader with num_workers > 0, pin_memory=True, and persistent_workers=True for GPU training
  • Set torch.backends.cudnn.benchmark = True for fixed input sizes

Read the full file on GitHub · 210 lines

Changes

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.

  1. 3d ago First seen · 210 lines · 81 tokens per session scan A 78eb1d933eb3

Subscribe to this mod's changes

ml-engineer is an agent published in the GitHub repository xvirobotics/metaskill (67 stars, last pushed 6mo ago), licensed MIT. It adds 81 tokens to every session and 2,217 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.