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/boards-work-item-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/boards-work-item-summary)<a href="https://agentmods.dev/skills/microsoft/azure-devops-skills/boards-work-item-summary"><img src="https://agentmods.dev/badge/skills/microsoft/azure-devops-skills/boards-work-item-summary/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/microsoft/azure-devops-skills/boards-work-item-summary"><img src="https://agentmods.dev/badge/skills/microsoft/azure-devops-skills/boards-work-item-summary.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.00025 | $0.00799 |
| Opus 5 | $0.00013 | $0.00400 |
| Sonnet 5 | $0.00005 | $0.00160 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
boards-work-item-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 9d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Get work item
This skill always works with one specific work item ID.
- If the user provides an ID (for example: "for 115770" or "work item 115770"), use that ID directly.
- If the user does not provide an ID, prompt the user once to provide the work item ID.
- If the ID is still not provided after prompting, stop and return a clear message stating that a work item ID is required and do not call any tools.
Tools
Use Azure DevOps MCP Server tools for all interactions with Azure DevOps.
wit_work_item(action:get): Get a work item from Azure DevOps by its ID.wit_work_item(action:list_comments): Get the list of comments for a work item by its ID.wit_work_item(action:get_batch): Get work item details in batch by their IDs. Use this tool to get the details of linked work items, using the links returned fromwit_work_itemwith actionget.
Steps
-
Call
wit_work_itemwith actiongetandexpand=allfor the requested ID so that you retrieve fields, relations, and links in a single call. -
If the work item has a parent (for example,
System.Parentor aSystem.LinkTypes.Hierarchy-Reverserelation), include the parent ID in the set of linked IDs to summarize. You do not need a separate call; instead, rely onwit_work_itemwith actionget_batchin the next step. -
From the work item
relationsarray, collect all linked work item IDs (parent, child, related, and any others). Callwit_work_itemwith actionget_batchonce with that list of IDs to get the details of all linked work items. -
Call
wit_work_itemwith actionlist_commentsonce to get the comments for the original work item.
Display results
When displaying the results:
-
Show the following fields for the main work item: Id, Title, State, Assigned To (just the display name, not the email), Work Item Type, Created Date formatted as
MM/DD/YYYY, Priority, and Tags. -
Provide a Links table. For each linked work item, display:
- Id as a clickable hyperlink in this exact format:
[{ID}](https://dev.azure.com/{organization}/{project}/_workitems/edit/{ID}) - Link type (for example: Parent, Child, Related, or the underlying relation name)
- Work item type
- Title
- State
- Id as a clickable hyperlink in this exact format:
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.
- 9d ago First seen · 54 lines · 25 tokens per session scan A d1817654dcac
boards-work-item-summary is a skill published in the GitHub repository microsoft/azure-devops-skills (44 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 799 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-08-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
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.