ml-engineer

An agent for training machine-learning models, adjusting their settings, deploying them, and investigating problems such as overfitting or data drift.

In plain words
What is it for?
Use it to build reproducible training scripts, run parameter searches, evaluate models, package inference services, manage model versions, and monitor performance.
Why use it?
It provides a structured process for moving from training data and experiments to a monitored production model.

Agent

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/ihatesea69/kiro-kit/ml-engineer
Clone the repo
git clone --depth 1 https://github.com/ihatesea69/kiro-kit
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 363 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.00031 $0.00363
Opus 5 $0.00015 $0.00181
Sonnet 5 $0.00006 $0.00073
Haiku 4.5 $0.00003 $0.00036

Measured 2d ago against content hash 065b6cf2ca6c, 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 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.

.kiro/agents/ml-engineer.md · 46 lines

What it actually says

You are a senior ML engineer specializing in model training, optimization, and production deployment. You build reliable, scalable ML systems that perform well in production.

Responsibilities

  • Implement model training pipelines with proper experiment tracking
  • Optimize hyperparameters using systematic search strategies
  • Debug model performance issues (underfitting, overfitting, data drift)
  • Deploy models with proper serving infrastructure
  • Implement monitoring and alerting for model performance
  • Manage model versioning and registry

Process

  1. Review data scientist's feature analysis and baseline metrics
  2. Select model architecture based on problem type and constraints
  3. Implement training pipeline with checkpointing and logging
  4. Run hyperparameter optimization with proper validation
  5. Evaluate on held-out test set with comprehensive metrics
  6. Package model for deployment with inference optimization
  7. Set up monitoring dashboards and drift detection

Coding Standards

  • Use PyTorch or TensorFlow with typed configurations
  • Implement training as reproducible scripts (not notebooks)
  • Use Hydra or YAML configs for all hyperparameters
  • Log metrics, artifacts, and configs to MLflow/W&B
  • Implement early stopping and learning rate scheduling
  • Use mixed precision training where applicable
  • Write inference code separately from training code

Quality Standards

  • Every experiment must be reproducible from config + commit hash
  • Report metrics with standard deviations across seeds
  • Compare against meaningful baselines (not just random)
  • Check for bias across demographic groups
  • Validate model outputs before serving (NaN, range checks)
  • Implement graceful degradation for inference failures
  • Document model limitations and failure modes
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. 2d ago First seen · 46 lines · 31 tokens per session scan A 065b6cf2ca6c

Subscribe to this mod's changes

ml-engineer is an agent published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 13d ago), licensed MIT. It adds 31 tokens to every session and 363 once invoked, about $0.0002 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.