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 selvarajmurugesan90/ops-engineering-skills --skill azure-pipelines-yaml-and-multi-stagegit clone --depth 1 https://github.com/selvarajmurugesan90/ops-engineering-skillsWrote 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/selvarajmurugesan90/ops-engineering-skills/azure-pipelines-yaml-and-multi-stage)<a href="https://agentmods.dev/skills/selvarajmurugesan90/ops-engineering-skills/azure-pipelines-yaml-and-multi-stage"><img src="https://agentmods.dev/badge/skills/selvarajmurugesan90/ops-engineering-skills/azure-pipelines-yaml-and-multi-stage/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/selvarajmurugesan90/ops-engineering-skills/azure-pipelines-yaml-and-multi-stage"><img src="https://agentmods.dev/badge/skills/selvarajmurugesan90/ops-engineering-skills/azure-pipelines-yaml-and-multi-stage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 30 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 298 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 301 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00110 | $0.02751 |
| Opus 5 | $0.00055 | $0.01375 |
| Sonnet 5 | $0.00022 | $0.00550 |
| Haiku 4.5 | $0.00011 | $0.00275 |
Grade A, and why
azure-pipelines-yaml-and-multi-stage 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 12d 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 — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Pipelines YAML and Multi-Stage Design
Purpose
Azure Pipelines (part of Azure DevOps) runs pipelines defined in
azure-pipelines.yml as a sequence of stages, each containing
jobs, each containing steps — with environments providing
approval gates and deployment history between stages, and templates
providing the reuse mechanism equivalent to GitHub Actions' reusable
workflows or GitLab's include:. This skill covers Azure Pipelines'
specific YAML schema, environment/approval mechanics, and template reuse
— not the generic pipeline-design concepts covered in
ci-cd-pipeline-design,
which apply here too but aren't repeated.
When to use
- Standing up a new pipeline for a repo hosted in Azure Repos, GitHub, or Bitbucket that needs to build/test/deploy through Azure DevOps.
- Designing a multi-stage pipeline (e.g. Build → Dev → Staging → Production) with approval gates and deployment history tracked per environment.
- Extracting a shared pipeline template so multiple repos consume one canonical build/deploy definition instead of copy-pasting YAML.
- Choosing between Microsoft-hosted agents (fast to start, ephemeral, cost per minute) and self-hosted agent pools (persistent, custom tooling, network access to private resources).
- Diagnosing a pipeline run stuck at a specific stage/job, a template parameter not resolving as expected, or an approval gate that isn't notifying the right approvers.
Prerequisites & environment
- An Azure DevOps organization and project, with a service connection configured for any external target (Azure subscription, Kubernetes cluster, container registry) the pipeline deploys to.
- Pipeline permissions: the pipeline's identity (or the service connection it uses) needs least-privilege access to only the resources it deploys to — not subscription-Owner-level access "to make it work."
- For self-hosted agents: a registered agent pool with agents that have network access to any private resources (internal artifact feeds, on-prem systems) the Microsoft-hosted pool can't reach.
- Environments (
Pipelines → Environments) created ahead of time if you want approval gates and deployment history — a stage'sdeploymentjob references an environment by name, and the environment must exist (and have its approval checks configured) before the first run.
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.
- 12d ago First seen · 302 lines · 110 tokens per session scan A 0f1fb8315eea
azure-pipelines-yaml-and-multi-stage is a skill published in the GitHub repository selvarajmurugesan90/ops-engineering-skills (39 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 110 tokens to every session and 2,751 once invoked, about $0.0006 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
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.
atmos-sbom
Atmos SBOM provenance: CycloneDX and SPDX generation from vendor and Terraform evidence, coverage diagnostics, NTIA validation, and native CI workflow-artifact publication.
atmos-version
Atmos Version Tracker: version tracks, lock files, managed external dependency versions, atmos version track commands, !version, file managers, update policy, pinning, and CI verification.
atmos-cache
Atmos caching: CI cache configuration and commands, GitHub Actions cache integration, Terraform registry cache mirror/list/prune/stats/trust, and cache modernization guidance.