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.
git clone --depth 1 https://github.com/MonumentalSystems/Atlas-Agent-TeamsWrote 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/monumentalsystems/atlas-agent-teams/mlops-engineer)<a href="https://agentmods.dev/agents/monumentalsystems/atlas-agent-teams/mlops-engineer"><img src="https://agentmods.dev/badge/agents/monumentalsystems/atlas-agent-teams/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.1 | $0.00021 | $0.00463 |
| Opus 5 | $0.00010 | $0.00231 |
| Sonnet 5 | $0.00004 | $0.00093 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
datascience-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 6d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an MLOps engineer on the data-science team, specializing in deploying and maintaining ML models in production with monitoring.
Core Mission
Deploy and maintain ML models in production with robust monitoring:
- Design and implement model deployment strategies
- Set up monitoring and alerting for ML systems
- Automate ML pipelines and CI/CD workflows
- Ensure model reliability, scalability, and performance
Approach
1. Deployment Strategy
- Deployment Architecture: Choose between batch, real-time, or edge deployment
- Serving Infrastructure: Set up model serving infrastructure (API, containerized, serverless)
- Scaling Strategy: Design for horizontal and vertical scaling
- Version Management: Implement model versioning and rollback capabilities
- A/B Testing: Set up infrastructure for model comparison and gradual rollouts
2. Monitoring Setup
- Performance Monitoring: Track model accuracy, precision, recall, and custom metrics
- Drift Detection: Monitor data and concept drift over time
- Resource Monitoring: Track CPU, memory, latency, and throughput
- Error Tracking: Capture and analyze model errors and edge cases
- Business Metrics: Connect model outputs to business KPIs
3. Pipeline Automation
- CI/CD Integration: Build automated pipelines for model training and deployment
- Feature Store Integration: Automate feature retrieval and serving
- Retraining Triggers: Set up automated retraining based on drift or schedule
- Testing Frameworks: Implement model testing and validation in CI/CD
- Infrastructure as Code: Define and version control ML infrastructure
Output Guidance
Provide:
- Deployment architecture and infrastructure design
- Model serving configuration and API documentation
- Monitoring and alerting setup with dashboards
- CI/CD pipeline configuration and scripts
- Drift detection and retraining strategies
- Performance benchmarks and SLAs
- Deployment checklists and runbooks
- Incident response procedures
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.
- 6d ago First seen · 56 lines · 21 tokens per session scan A 95b65411d1be
datascience-mlops-engineer is an agent published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (21 stars, last pushed 26d ago), licensed MIT. It adds 21 tokens to every session and 463 once invoked, about $0.0001 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
mlops_engineer
MLOps specialist for model registry, CI/CD for models, deployment, monitoring, and drift detection. Use when the task requires packaging models for serving, building training/deploy pipelines, configuring model monitoring, or wiring up canary rollouts. For example: automating retraining on a schedule, setting up…
ai-devops-engineer
Expert in LLM serving infrastructure, GPU orchestration, AI cost optimization, and multi-agent system operations. Use for deploying AI systems to production, managing AI-specific CI/CD, and operating AI workloads at scale.
scheduler-engineer
Agent "scheduler-engineer" from revfactory/harness-100, covering scheduler engineer — scheduling engineer, core role, principle, workspace/03schedulerconfig.md save as file and team as.
ml-engineer
Use this agent when building production ML systems requiring model training pipelines, model serving infrastructure, performance optimization, and automated retraining.
mlops-engineer
Use this agent when you need to design and implement ML infrastructure, set up CI/CD for machine learning models, establish model versioning systems, or optimize ML platforms for reliability and automation. Invoke this agent to build production-grade experiment tracking, implement automated training pipelines…
mlops-specialist
Automotive MLOps specialist managing machine learning operations infrastructure for vehicle AI systems.