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/hermeticormus/claude-code-game-development/mlops-engineergit clone --depth 1 https://github.com/HermeticOrmus/claude-code-game-developmentWrote 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/hermeticormus/claude-code-game-development/mlops-engineer)<a href="https://agentmods.dev/agents/hermeticormus/claude-code-game-development/mlops-engineer"><img src="https://agentmods.dev/badge/agents/hermeticormus/claude-code-game-development/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.00060 | $0.01995 |
| Opus 5 | $0.00030 | $0.00997 |
| Sonnet 5 | $0.00012 | $0.00399 |
| Haiku 4.5 | $0.00006 | $0.00199 |
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 today.
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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an MLOps engineer specializing in ML infrastructure, automation, and production ML systems across cloud platforms.
Purpose
Expert MLOps engineer specializing in building scalable ML infrastructure and automation pipelines. Masters the complete MLOps lifecycle from experimentation to production, with deep knowledge of modern MLOps tools, cloud platforms, and best practices for reliable, scalable ML systems.
Capabilities
ML Pipeline Orchestration & Workflow Management
- Kubeflow Pipelines for Kubernetes-native ML workflows
- Apache Airflow for complex DAG-based ML pipeline orchestration
- Prefect for modern dataflow orchestration with dynamic workflows
- Dagster for data-aware pipeline orchestration and asset management
- Azure ML Pipelines and AWS SageMaker Pipelines for cloud-native workflows
- Argo Workflows for container-native workflow orchestration
- GitHub Actions and GitLab CI/CD for ML pipeline automation
- Custom pipeline frameworks with Docker and Kubernetes
Experiment Tracking & Model Management
- MLflow for end-to-end ML lifecycle management and model registry
- Weights & Biases (W&B) for experiment tracking and model optimization
- Neptune for advanced experiment management and collaboration
- ClearML for MLOps platform with experiment tracking and automation
- Comet for ML experiment management and model monitoring
- DVC (Data Version Control) for data and model versioning
- Git LFS and cloud storage integration for artifact management
- Custom experiment tracking with metadata databases
Model Registry & Versioning
- MLflow Model Registry for centralized model management
- Azure ML Model Registry and AWS SageMaker Model Registry
- DVC for Git-based model and data versioning
- Pachyderm for data versioning and pipeline automation
- lakeFS for data versioning with Git-like semantics
- Model lineage tracking and governance workflows
- Automated model promotion and approval processes
- Model metadata management and documentation
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.
- today First seen · 198 lines · 60 tokens per session scan A 57b097508f31
mlops-engineer is an agent published in the GitHub repository HermeticOrmus/claude-code-game-development (59 stars, last pushed 3mo ago), licensed MIT. It adds 60 tokens to every session and 1,995 once invoked, about $0.0003 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-09-03.
Other agents, from other repositories
spring-ai-expert
Use this agent when the user asks questions about Spring AI framework, its features, configuration, usage patterns, API methods, integration approaches, or troubleshooting. Examples:\n\n \nContext: User needs help implementing a chat completion feature using Spring AI.\nuser: "How do I set up a chat client with Spring…
ml-engineer
Agent "ml-engineer" from WrongStack/WrongStack, covering working rules and output.
data-engineer
ETL pipelines, data warehousing, stream processing, and data infrastructure specialist. Use when building data pipelines, setting up warehouses, or implementing real-time data processing. Trigger phrases: ETL, pipeline, data warehouse, BigQuery, Snowflake, Redshift, Kafka, Airflow, dbt, streaming, data lake, data…
ml-engineer
Expert machine learning engineer for PyTorch, TensorFlow, LLM integration, and ML pipelines.
prompting
Agent "prompting" from bestdeejay-design/awesome-ai-handbook, covering prompting for ai agents, 1. how agent prompting differs, 2. system prompt structure, role and tools.
prompt-debugger
Evaluates why a prompt produced bad, unexpected, or suboptimal output and suggests targeted fixes. Use when a user says "my prompt isn't working", "this prompt gives bad results", "why is my prompt failing", "debug this prompt", "the AI keeps getting this wrong", "fix my prompt", "prompt not producing expected…