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 agents/morganmuli/metaskill/ml-engineergit clone --depth 1 https://github.com/morganmuli/metaskillWhat 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.00081 | $0.02217 |
| Opus 5 | $0.00041 | $0.01108 |
| Sonnet 5 | $0.00016 | $0.00443 |
| Haiku 4.5 | $0.00008 | $0.00222 |
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 2d 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.
This is a copy
100% identical to ml-engineer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.Modulesubclasses with clear forward signatures - Use
@dataclassor PydanticBaseModelfor model configuration -- never pass raw dicts - Implement proper weight initialization (Xavier/Glorot for linear layers, Kaiming for ReLU networks)
- Use
nn.Sequential,nn.ModuleList, andnn.ModuleDictfor dynamic architectures - For transformer-based models, leverage
torch.nn.TransformerEncoderor Hugging Facetransformerswhen 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.autocastandtorch.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.DataLoaderwithnum_workers > 0,pin_memory=True, andpersistent_workers=Truefor GPU training - Set
torch.backends.cudnn.benchmark = Truefor fixed input sizes
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.
- 2d ago First seen · 210 lines · 81 tokens per session scan A 78eb1d933eb3
ml-engineer is an agent published in the GitHub repository morganmuli/metaskill (1 stars, last pushed 3d 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. It is 100% identical to ml-engineer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
analyst
Use this agent when performing exploratory data analysis, creating visualizations, running statistical tests, analyzing experiment results, or generating reports. For example: profiling a new dataset, creating distribution plots, running hypothesis tests on A/B experiment data, comparing model metrics across…
test-engineer
Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.
ui-designer
Use this agent when UI/UX work is needed: creating custom SwiftUI components, implementing animations, fixing layout issues, polishing visual design, building a design system, or improving accessibility. For example: adding a custom tab bar animation, implementing a skeleton loading view, auditing VoiceOver support…
code-reviewer
Use this agent when code changes need review before completion. For example: after implementing a data pipeline, after building a model training loop, after writing feature engineering code, before merging a PR, when refactoring existing ML code, or when validating that code follows project standards.
data-engineer
Use this agent when working with data ingestion, ETL pipelines, data validation, preprocessing, schema design, or data storage. For example: building a data loading pipeline from CSV/Parquet, adding pandera schema validation, creating preprocessing transforms, setting up DVC for data versioning, optimizing data…
ml-engineer
Use this agent when working with model architecture, training loops, loss functions, optimizers, hyperparameter tuning, experiment tracking, or model evaluation. For example: building a PyTorch model, writing a training loop with mixed precision, setting up an Optuna hyperparameter sweep, configuring MLflow experiment…