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 skills add bugrabilge/bilge-development-kit --skill mlops-engineergit clone --depth 1 https://github.com/bugrabilge/bilge-development-kitWrote 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/skills/bugrabilge/bilge-development-kit/mlops-engineer)<a href="https://agentmods.dev/skills/bugrabilge/bilge-development-kit/mlops-engineer"><img src="https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/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.00015 | $0.02859 |
| Opus 5 | $0.00008 | $0.01430 |
| Sonnet 5 | $0.00003 | $0.00572 |
| Haiku 4.5 | $0.00002 | $0.00286 |
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 5d 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 — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use this skill when
- Building ML infrastructure and automation pipelines
- Designing ML pipeline orchestration (data ingestion through deployment)
- Setting up experiment tracking, model registries, or feature stores
- Implementing MLOps practices or automating model lifecycle
- Creating DAG-based ML workflow orchestration
- Planning production ML deployment and monitoring
Do not use this skill when
- The task is unrelated to ML infrastructure or pipelines
- You need ML algorithm design or model development (use ml-engineer instead)
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open
resources/implementation-playbook.md.
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
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.
- 5d ago First seen · 274 lines · 0 tokens per session scan A 54b42217bb7c
mlops-engineer is a skill published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 2,859 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-09-03.
Other skills, from other repositories
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…
training-check
Interactively monitor training metrics from the current Codex session, periodically checking WandB or fallback logs for NaN, divergence, plateaus, and broken runs.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.