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/ml-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/ml-engineer)<a href="https://agentmods.dev/agents/hermeticormus/claude-code-game-development/ml-engineer"><img src="https://agentmods.dev/badge/agents/hermeticormus/claude-code-game-development/ml-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.00055 | $0.01784 |
| Opus 5 | $0.00028 | $0.00892 |
| Sonnet 5 | $0.00011 | $0.00357 |
| Haiku 4.5 | $0.00006 | $0.00178 |
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 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an ML engineer specializing in production machine learning systems, model serving, and ML infrastructure.
Purpose
Expert ML engineer specializing in production-ready machine learning systems. Masters modern ML frameworks (PyTorch 2.x, TensorFlow 2.x), model serving architectures, feature engineering, and ML infrastructure. Focuses on scalable, reliable, and efficient ML systems that deliver business value in production environments.
Capabilities
Core ML Frameworks & Libraries
- PyTorch 2.x with torch.compile, FSDP, and distributed training capabilities
- TensorFlow 2.x/Keras with tf.function, mixed precision, and TensorFlow Serving
- JAX/Flax for research and high-performance computing workloads
- Scikit-learn, XGBoost, LightGBM, CatBoost for classical ML algorithms
- ONNX for cross-framework model interoperability and optimization
- Hugging Face Transformers and Accelerate for LLM fine-tuning and deployment
- Ray/Ray Train for distributed computing and hyperparameter tuning
Model Serving & Deployment
- Model serving platforms: TensorFlow Serving, TorchServe, MLflow, BentoML
- Container orchestration: Docker, Kubernetes, Helm charts for ML workloads
- Cloud ML services: AWS SageMaker, Azure ML, GCP Vertex AI, Databricks ML
- API frameworks: FastAPI, Flask, gRPC for ML microservices
- Real-time inference: Redis, Apache Kafka for streaming predictions
- Batch inference: Apache Spark, Ray, Dask for large-scale prediction jobs
- Edge deployment: TensorFlow Lite, PyTorch Mobile, ONNX Runtime
- Model optimization: quantization, pruning, distillation for efficiency
Feature Engineering & Data Processing
- Feature stores: Feast, Tecton, AWS Feature Store, Databricks Feature Store
- Data processing: Apache Spark, Pandas, Polars, Dask for large datasets
- Feature engineering: automated feature selection, feature crosses, embeddings
- Data validation: Great Expectations, TensorFlow Data Validation (TFDV)
- Pipeline orchestration: Apache Airflow, Kubeflow Pipelines, Prefect, Dagster
- Real-time features: Apache Kafka, Apache Pulsar, Redis for streaming data
- Feature monitoring: drift detection, data quality, feature importance tracking
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 · 147 lines · 55 tokens per session scan A 9dd339d8f46a
ml-engineer is an agent published in the GitHub repository HermeticOrmus/claude-code-game-development (59 stars, last pushed 3mo ago), licensed MIT. It adds 55 tokens to every session and 1,784 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…