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/payrequest/claude-plugins/mlops-engineergit clone --depth 1 https://github.com/PayRequest/claude-pluginsWhat 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.01994 |
| 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- mlops-engineer — 100% identical, 2 lines differ
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.
- 2d ago First seen · 198 lines · 60 tokens per session scan A 60a38dec3069
mlops-engineer is an agent published in the GitHub repository PayRequest/claude-plugins (11 stars, last pushed 10mo ago), licensed MIT. It adds 60 tokens to every session and 1,994 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-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.