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/jnPiyush/AgentXnpx agentmods add skills/jnpiyush/agentx/yaml-pipelinesWrote 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/jnpiyush/agentx/yaml-pipelines)<a href="https://agentmods.dev/skills/jnpiyush/agentx/yaml-pipelines"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/yaml-pipelines/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/jnpiyush/agentx/yaml-pipelines"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/yaml-pipelines.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.03077 |
| Opus 5.5 | $0.00021 | $0.01231 |
| Sonnet 5.5 | $0.00011 | $0.00615 |
| Haiku 4.5 | $0.00005 | $0.00308 |
Grade A, and why
yaml-pipelines 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 1mo 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 — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YAML Pipelines & CI/CD Configuration
Purpose: Quick-reference guide for YAML-based CI/CD pipelines. Start here for platform selection, core patterns, and best practices. Dive into reference files for full examples.
When to Use This Skill
- Creating Azure DevOps YAML pipelines
- Configuring GitLab CI/CD pipelines
- Designing multi-stage deployment pipelines
- Implementing pipeline templates and variable groups
- Managing pipeline secrets and caching
Prerequisites
- Azure DevOps or GitLab project access
- YAML syntax knowledge
- CI/CD concepts understanding
Platform Comparison - Start Here
| Feature | Azure Pipelines | GitLab CI | GitHub Actions |
|---|---|---|---|
| Config File | azure-pipelines.yml |
.gitlab-ci.yml |
.github/workflows/*.yml |
| Stages | [PASS] Native | [PASS] Native | [WARN] Jobs only |
| Templates | [PASS] Full support | [PASS] Includes/Extends | [PASS] Reusable workflows |
| Caching | [PASS] Cache task | [PASS] Built-in | [PASS] actions/cache |
| Environments | [PASS] Native | [PASS] Native | [PASS] Native |
| Approvals | [PASS] Environment gates | [PASS] Manual when |
[PASS] Environment rules |
| Matrix | [PASS] strategy.matrix |
[PASS] parallel.matrix |
[PASS] strategy.matrix |
| Secrets | [PASS] Variable groups | [PASS] CI/CD Variables | [PASS] Secrets |
| Self-hosted | [PASS] Agent pools | [PASS] Runners | [PASS] Self-hosted runners |
| Best for | Azure-heavy orgs | All-in-one DevOps | Open source / GitHub |
Decision Tree - Choosing a Platform
Is your code hosted on GitHub?
+- YES -> Use GitHub Actions (see ../github-actions-workflows/SKILL.md)
+- NO
| +- Using Azure DevOps for work items & repos?
| | - YES -> Use Azure Pipelines
| +- Using GitLab for repos & issue tracking?
| | - YES -> Use GitLab CI/CD
| - Need multi-platform or hybrid?
| - Use Azure Pipelines (broadest agent/pool support)
Key considerations:
- Azure Pipelines: Best native integration with Azure services, variable groups, service connections, and approval gates.
- GitLab CI: Tightest integration when you already use GitLab for SCM + issues + registry.
- GitHub Actions: Ideal for open-source and GitHub-native workflows (covered in its own skill).
What ships with it
5 files 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.
- 1mo ago Changed 500c37a058eb
- 1mo ago First seen · 361 lines · 53 tokens per session scan A cf46ee33db3d
yaml-pipelines is a skill published in the GitHub repository jnPiyush/AgentX (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 53 tokens to every session and 3,077 once invoked, about $0.0002 per session on Opus 5.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
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.