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/pjt222/agent-almanac/mlops-engineergit clone --depth 1 https://github.com/pjt222/agent-almanacWrote 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.
[](https://agentmods.dev/agents/pjt222/agent-almanac/mlops-engineer)<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="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00031 | $0.02235 |
| Opus 5 | $0.00015 | $0.01118 |
| Sonnet 5 | $0.00006 | $0.00447 |
| Haiku 4.5 | $0.00003 | $0.00224 |
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 4d 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.
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 approvalsdeploy-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 pipelinesorchestrate-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 testingsetup-automl-pipeline— Optuna / Ray Tune hyperparameter optimizationdetect-anomalies-aiops— Time series anomaly detection and alert correlationforecast-operational-metrics— Prophet / statsmodels capacity forecastinglabel-training-data— Label Studio annotation workflows and agreement metricsbenchmark-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, alongsiderun-ab-test-modelsandlabel-training-data)
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.
- 4d ago First seen · 210 lines · 31 tokens per session scan A 38a7496e163d
mlops-engineer is an agent published in the GitHub repository pjt222/agent-almanac (32 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 2,235 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.
Other agents, from other repositories
ml-engineer
Build production ML systems with PyTorch 2.x, TensorFlow, and modern ML frameworks. Implements model serving, feature engineering, A/B testing, and monitoring. Use PROACTIVELY for ML model deployment, inference optimization, or production ML infrastructure.
ml-engineer
Implement ML pipelines, model serving, and feature engineering. Handles TensorFlow/PyTorch deployment, A/B testing, and monitoring. Use proactively for ML model integration or production deployment.
mlops-engineer
Build ML pipelines, experiment tracking, and model registries. Implements MLflow, Kubeflow, and automated retraining. Handles data versioning and reproducibility. Use proactively for ML infrastructure, experiment management, or pipeline automation.
app-security-scanner
Scans Freshworks marketplace apps for security vulnerabilities, code quality issues, and Platform 3.0 compliance. Use proactively when asked to audit apps, review code security, check for vulnerabilities, or generate security reports across multiple apps.
planner
你是任务规划师。擅长将设计方案拆解为可执行的子任务,管理优先级和实施顺序。你确保每个任务边界清晰、可独立完成。.
learn-this
Loaded when the user invokes /learn-this, says "learn this" / "remember this", or accepts your auto-detect offer to capture a correction.