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-my-work/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-my-work)<a href="https://agentmods.dev/skills/microsoft/azure-devops-skills/boards-my-work"><img src="https://agentmods.dev/badge/skills/microsoft/azure-devops-skills/boards-my-work.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.00060 | $0.00770 |
| Opus 5 | $0.00030 | $0.00385 |
| Sonnet 5 | $0.00012 | $0.00154 |
| Haiku 4.5 | $0.00006 | $0.00077 |
Grade A, and why
boards-my-work 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Get my work items
Before getting work items, you need to know which project to use.
- If the user provides a project name in their request (for example, "for Contoso"), use that project directly and do not call the
core_list_projectstool. - If a project name is not provided, first return a prompt asking the user for the project name.
- If the project name is still not provided after prompting the user, then call the MCP Server tool
core_list_projectsto get the list of projects the user can choose from. - Do not continue if the user has not provided a project name or selected one from the list.
Tools
Use Azure DevOps MCP Server tools for all interactions with Azure DevOps.
core_list_projects: Get the list of projects the user can choose from.wit_work_item(action:my): Get work items from Azure DevOps that are assigned to the userwit_work_item(action:get_batch): Get work item details in batch by their IDs. Use this tool to get detailed information about the work items retrieved bywit_work_itemwith actionmy.
Fields
When using the tool wit_work_item with action get_batch, if the user does not provide a list of fields to retrieve, use the following default fields:
- System.Id
- System.Title
- System.State
- System.AssignedTo
- System.WorkItemType
- System.CreatedDate
- System.ChangedDate
- System.Tags
- Microsoft.VSTS.Common.Priority
Display results
When displaying the results...
- show the work item ID (make this clickable hyperlink to open the work item in a web browser. Format should be like this: {ID}),
- title
- state,
- priority
in a table format. Show the most recently changed work items first and group the work items by thier work item type (System.WorkItemType). For example, group the work items into the following categories based on their work item type:
Epics Features Stories Bugs Tasks Test Cases other work item types
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 · 65 lines · 60 tokens per session scan A 5e9e526dc952
boards-my-work is a skill published in the GitHub repository microsoft/azure-devops-skills (44 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 770 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
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.