Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Omar-Obando/qwen-orchestratornpx agentmods add skills/omar-obando/qwen-orchestrator/devops-pipelineWrote 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/omar-obando/qwen-orchestrator/devops-pipeline)<a href="https://agentmods.dev/skills/omar-obando/qwen-orchestrator/devops-pipeline"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/devops-pipeline/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/omar-obando/qwen-orchestrator/devops-pipeline"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/devops-pipeline.svg" alt="Reviewed on agentmods" width="80" 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.00060 | $0.03540 |
| Opus 5 | $0.00030 | $0.01770 |
| Sonnet 5 | $0.00012 | $0.00708 |
| Haiku 4.5 | $0.00006 | $0.00354 |
Grade A, and why
devops-pipeline 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 10d 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 — 599 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Pipeline Skill — CI/CD and Deployment Strategies
Overview
This skill provides comprehensive guidance for designing and implementing CI/CD pipelines, deployment strategies, infrastructure as code, monitoring setup, and DevOps best practices. It includes GitHub Actions, Docker, Kubernetes, and deployment patterns. Based on Azure DevOps, CODING DevOps, and DevOps certification standards.
When to Use
Use this skill when:
- Designing CI/CD pipelines for any project
- Setting up deployment strategies (blue-green, canary, rolling)
- Configuring infrastructure as code (Terraform, CloudFormation)
- Implementing monitoring and alerting (Prometheus, Grafana)
- Optimizing deployment processes
- Managing cloud infrastructure (AWS, Azure, GCP)
- Setting up GitHub Actions workflows
- Configuring Docker containers and images
- Implementing Kubernetes deployments
- Creating Helm charts for Kubernetes
- Setting up container registries
- Implementing container security scanning
- Configuring CI/CD pipeline caching
- Setting up pipeline secrets management
- Implementing pipeline as code
- Creating multi-stage pipeline strategies
- Setting up deployment environments
- Implementing rollback strategies
- Creating deployment documentation
- Building deployment monitoring dashboards
- Setting up deployment alerting
- Implementing deployment security gates
- Creating deployment automation scripts
Do NOT use this skill when:
- Writing application code (use developer skill or specific framework skill)
- Database schema design (use database design skill)
- UI/UX design (use frontend design skill)
- Writing specific test cases (use testing-strategy skill)
- Implementing business logic (use developer skill)
CI/CD Pipeline Stages
┌─────────────────────────────────────────────────────────────┐
│ CI/CD Pipeline │
├─────────────────────────────────────────────────────────────┤
│ 1. Checkout │
│ 2. Install Dependencies │
│ 3. Lint & Format Check │
│ 4. Type Checking │
│ 5. Unit Tests │
│ 6. Integration Tests │
│ 7. Build │
│ 8. Security Scan │
│ 9. E2E Tests (optional) │
│ 10. Deploy (Staging) │
│ 11. E2E Tests (Staging) │
│ 12. Deploy (Production) │
└─────────────────────────────────────────────────────────────┘
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 599 lines · 60 tokens per session scan A ad745f3974c8
devops-pipeline is a skill published in the GitHub repository Omar-Obando/qwen-orchestrator (49 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 3,540 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 skills, from other repositories
aplicacao-de-tecnologias-de-devops
Ensina como implementar práticas de DevOps utilizando ferramentas como Docker, Kubernetes e Jenkins.
DevOps Avançado com Jenkins e Docker
Implementação de práticas de DevOps utilizando Jenkins e Docker.
devops-com-kubernetes
Aprenda a automatizar pipelines de entrega contínua e garantir a escalabilidade de aplicativos utilizando Kubernetes e ferramentas de DevOps como Jenkins e GitLab CI/CD.
Implementacao-de-DevOps-Com-Jenkins-e-Docker
O objetivo desta skill é ensinar como implementar práticas de DevOps utilizando Jenkins e Docker, incluindo a configuração de pipelines de entrega contínua e a orquestração de contêineres. Com isso, os participantes poderão entender como automatizar e otimizar o processo de desenvolvimento e entrega de software.
devops-com-jenkins-e-docker
Guia prático para implementação de pipelines de entrega contínua utilizando Jenkins e Docker.
devops-para-ambientes-de-containers
O objetivo deste guia é fornecer uma visão geral de como implementar práticas DevOps em ambientes que utilizam contêineres, garantindo a entrega contínua e confiável de software.