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/engineerwithai/engineerwith-agents/ml-engineergit clone --depth 1 https://github.com/EngineerWithAI/engineerwith-agentsWrote 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/engineerwithai/engineerwith-agents/ml-engineer)<a href="https://agentmods.dev/agents/engineerwithai/engineerwith-agents/ml-engineer"><img src="https://agentmods.dev/badge/agents/engineerwithai/engineerwith-agents/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.01783 |
| 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 yesterday.
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.
- yesterday First seen · 147 lines · 55 tokens per session scan A 561214802cd3
ml-engineer is an agent published in the GitHub repository EngineerWithAI/engineerwith-agents (4 stars, last pushed 7mo ago), licensed MIT. It adds 55 tokens to every session and 1,783 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
kth
Cloud-native engineer and educator. Co-author of Kubernetes Up & Running (2017, 2019). Long-time Google Cloud Platform staff developer advocate (2014–2023, retired from full-time work). Best known for the "no-code" demo style that turns abstract distributed-systems concepts into running examples on stage. Authored…
infra-specialist
Use for isolated Terraform, Docker, AWS, Azure, and deployment-documentation work across terraform/, aws/, docker-compose.yml, DEPLOYMENT.md, and agenticai/deployments/.
infra-guardian
Infrastructure validator that blocks deployments on config drift.
openclaw-on-azure
Deploy, configure, operate, and troubleshoot a secure hosted OpenClaw AI assistant on Azure (Container Apps + Azure OpenAI in Foundry Models, passwordless Managed Identity, Entra ID Easy Auth, optional Microsoft Teams). Point it at this repo and ask in plain English — it drives the devclaw/azd workflow for you.
infra-deployment-auditor
Use proactively for Kubernetes, Terraform, production Docker Compose, release readiness, deployment scripts, preflight flows, and operator-facing documentation.
helm-config-validator
Validates Helm chart configurations across CPP environments. Detects secrets in values, missing environment overrides, configuration drift, and misconfigured resources. user: "Validate the Helm chart config for cpp-hearing across all environments" assistant: "I'll use the helm-config-validator agent to check for…