mlops-engineer

mlops-engineer is an agent for Claude Code from pjt222/agent-almanac. It costs 31 tokens per session (2,235 once invoked), scanned A, original, MIT.

An ML operations specialist for running machine-learning work from experiments through production. ML operations, or MLOps, covers tracking models and data, automating pipelines, serving predictions, and monitoring deployed systems.

In plain words
What is it for?
Use it to set up experiment tracking, model registries, feature stores, dataset versioning, automated pipelines, prediction APIs, drift detection, and anomaly alerts.
Why use it?
It helps turn experimental models into repeatable services that can be versioned, deployed, and checked for changing data or performance.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; mentions CLAUDE.md; mentions subagents.

Part of the agent-almanac plugin — 122 skills, 77 agents shipped together

Good fit Use it to set up experiment tracking, model registries, feature stores, dataset versioning, automated pipelines, prediction APIs, drift detection, and anomaly alerts.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/pjt222/agent-almanac/mlops-engineer
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.

Clone the repo
git clone --depth 1 https://github.com/pjt222/agent-almanac

Made for: Claude Code.

Or install agent-almanac, the plugin that ships this one along with the rest of its 122 skills, 77 agents.

Wrote 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.

agentmods badge for mlops-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/pjt222/agent-almanac/mlops-engineer/github.svg)](https://agentmods.dev/agents/pjt222/agent-almanac/mlops-engineer)
Your own site
<a href="https://agentmods.dev/agents/pjt222/agent-almanac/mlops-engineer"><img src="https://agentmods.dev/badge/agents/pjt222/agent-almanac/mlops-engineer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for mlops-engineer

Your own site · 80×15
<a href="https://agentmods.dev/agents/pjt222/agent-almanac/mlops-engineer"><img src="https://agentmods.dev/badge/agents/pjt222/agent-almanac/mlops-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 2,235 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00031 $0.02235
Opus 5.5 $0.00012 $0.00894
Sonnet 5.5 $0.00006 $0.00447
Haiku 4.5 $0.00003 $0.00224

Measured 1mo ago against content hash 38a7496e163d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mlops-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 1mo 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.

agents/mlops-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.

MLOps Engineer Agent

An ML operations agent specializing in the full ML lifecycle: experiment tracking, model registry, feature engineering, pipeline orchestration, model serving, drift monitoring, and AIOps. Uses open-source tooling (MLflow, DVC, Feast, Evidently, Optuna, Prefect).

Purpose

This agent bridges the gap between data science experimentation and production ML systems. It handles the operational concerns of deploying, monitoring, and maintaining ML models at scale: reproducible experiments, versioned data and models, automated pipelines, real-time serving, drift detection, and anomaly-based alerting.

Capabilities

  • Experiment Tracking: MLflow tracking server setup, autologging, run comparison, artifact management
  • Model Registry: Model versioning, stage transitions (Staging → Production), approval workflows
  • Model Serving: REST/gRPC endpoints via MLflow, BentoML, or Seldon Core with autoscaling
  • Feature Engineering: Feast feature store with offline/online stores and point-in-time joins
  • Data Versioning: DVC for dataset versioning, remote storage backends, reproducible pipelines
  • Pipeline Orchestration: Prefect/Airflow DAGs with retry logic, scheduling, and dependency management
  • Drift Monitoring: Evidently AI reports for data drift (PSI, KS test) and concept drift detection
  • A/B Testing: Traffic splitting, canary/shadow deployments, statistical significance testing
  • AutoML: Optuna/Ray Tune hyperparameter optimization with Hyperband/ASHA schedulers
  • AIOps: Time series anomaly detection, alert correlation, operational metric forecasting

Available Skills

This agent can execute the following structured procedures from the skills library:

Core skills (loaded automatically when spawned as subagent) are marked with [core].

MLOps

  • track-ml-experiments — MLflow tracking server, autologging, run comparison [core]
  • register-ml-model — MLflow Model Registry with stage transitions and approvals
  • deploy-ml-model-serving — MLflow / BentoML / Seldon Core REST/gRPC endpoints [core]
  • build-feature-store — Feast offline/online stores with feature definitions [core]
  • version-ml-data — DVC data versioning with remote storage and pipelines
  • orchestrate-ml-pipeline — Prefect / Airflow DAG construction with retry logic [core]
  • monitor-model-drift — Evidently AI drift detection with PSI and KS tests [core]
  • run-ab-test-models — Traffic splitting, canary/shadow deployment, significance testing
  • setup-automl-pipeline — Optuna / Ray Tune hyperparameter optimization
  • detect-anomalies-aiops — Time series anomaly detection and alert correlation
  • forecast-operational-metrics — Prophet / statsmodels capacity forecasting
  • label-training-data — Label Studio annotation workflows and agreement metrics
  • benchmark-htr-engines — Select an OCR/HTR engine by scoring candidates on the same labelled samples (raw CER, lenient CER, WER, and a critical name/date token diff); secondary model-selection tooling here — primary home is nlp-specialist (metrics / text-processing), while this agent's angle is deployment-side engine selection and re-ranking engines after new models ship (drift-adjacent, alongside run-ab-test-models and label-training-data)

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. 1mo ago First seen · 210 lines · 31 tokens per session scan A 38a7496e163d

Subscribe to this mod's changes

mlops-engineer is an agent published in the GitHub repository pjt222/agent-almanac (42 stars, last pushed 4d ago), licensed MIT. It adds 31 tokens to every session and 2,235 once invoked, about $0.0001 per session on Opus 5.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.