Azure DevOps Skills is a collection of reusable instruction bundles that teach AI coding assistants how to perform recurring Azure DevOps tasks. The examples support workflows such as reviewing backlogs, listing active work, and managing iterations through the Azure DevOps MCP server.
Borrowing it
Nothing to install: this file belongs to microsoft/azure-devops-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/microsoft/azure-devops-skills/main/.github/skills/pipelines-build-summary/SKILL.mdgit clone --depth 1 https://github.com/microsoft/azure-devops-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/microsoft/azure-devops-skills/pipelines-build-summary)<a href="https://agentmods.dev/skills/microsoft/azure-devops-skills/pipelines-build-summary"><img src="https://agentmods.dev/badge/skills/microsoft/azure-devops-skills/pipelines-build-summary.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.00050 | $0.01250 |
| Opus 5 | $0.00025 | $0.00625 |
| Sonnet 5 | $0.00010 | $0.00250 |
| Haiku 4.5 | $0.00005 | $0.00125 |
Grade A, and why
pipelines-build-summary 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 8d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline build summary
This skill works in the context of a project. A pipeline definition or build ID is optional and depends on what the user asks.
Project selection
- If the user provides a project name in their request (for example, "for Contoso"), use that project directly and do not call
core_list_projects. - If the user does not provide a project name, first ask the user once to provide the project name.
- If the project name is still not provided after asking once, call
core_list_projectsto return a list of projects the user can choose from.
Pipeline definition selection
- If the user provides a pipeline or definition name, use
pipelines_definitionwith actionlistand anamefilter to find it. - If the user does not specify a pipeline and the request requires one (for example, "show recent builds"), ask the user once for the pipeline name.
- If the pipeline name is still not provided after asking once, call
pipelines_definitionwith actionlistto list available definitions for the user to choose from.
Tools
Use Azure DevOps MCP Server tools for all interactions with Azure DevOps.
core_list_projects: Get a list of projects in the organization.pipelines_definition(action:list): Get a list of build/pipeline definitions for a project.pipelines_build(action:list): Get a list of builds, optionally filtered by definition, branch, or status.pipelines_build(action:get_status): Get the status and result of a specific build by ID.pipelines_build_log(action:list): Get the list of logs for a specific build.pipelines_build_log(action:get_content): Get a specific log by log ID for a build (use to retrieve failed step logs).pipelines_build(action:get_changes): Get the commits/changes associated with a specific build.
Rules
1. List recent builds for a pipeline
- When the user asks to list builds or show recent builds for a pipeline, call
pipelines_buildwith actionlistfiltered by the definition ID. - Optionally filter by
branchName,statusFilter, orresultFilterif the user specifies (for example, "failed builds on main"). - Do not fetch logs or changes unless the user asks.
- Show the results in a table.
- If there are no builds, explicitly state that there are no builds for this pipeline.
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.
- 8d ago First seen · 104 lines · 50 tokens per session scan A 6ef38786608d
pipelines-build-summary is a skill published in the GitHub repository microsoft/azure-devops-skills (44 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 1,250 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
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
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.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
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.
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.