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/work-iterations/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/work-iterations)<a href="https://agentmods.dev/skills/microsoft/azure-devops-skills/work-iterations"><img src="https://agentmods.dev/badge/skills/microsoft/azure-devops-skills/work-iterations/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/work-iterations"><img src="https://agentmods.dev/badge/skills/microsoft/azure-devops-skills/work-iterations.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.00019 | $0.01203 |
| Opus 5.5 | $0.00008 | $0.00481 |
| Sonnet 5.5 | $0.00004 | $0.00241 |
| Haiku 4.5 | $0.00002 | $0.00120 |
Grade A, and why
work-iterations 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Instructions
This skill always works in the context of a project. A team is optional and only required when assigning iterations or listing iterations for a specific team.
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.
Team selection
- If the team is not provided, only perform actions that require project-only context (list or create project-level iterations). Do not attempt to assign iterations.
- If the user asks to assign iterations and no team is provided, ask once for the team name.
- If the team name is still not provided after asking once, call
core_list_project_teamsfor the selected project so the user can pick a team.
Tools
Use Azure DevOps MCP Server tools for all interactions with Azure DevOps.
core_list_projects: Get a list of projects in the organization.core_list_project_teams: Get a list of teams for a project.work_iteration_write(action:create): Create iterations in the project.work_iteration_write(action:assign): Assign iterations to a team.work(action:list_team_iterations): List iterations currently assigned to a team.work(action:list_iterations): List iterations for the project.
Rules
1. List iterations for a project
- When the user asks only to list iterations for a project, call
workwith actionlist_iterationsfor that project. - Do not call
work_iteration_writein this case. - Show the results in a list, including iteration name and dates.
- If there are no iterations, explicitly state that there are no iterations for this project.
Example
- "list iterations for project Contoso"
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 First seen · 102 lines · 19 tokens per session scan A a0efa14bd50f
work-iterations is a skill published in the GitHub repository microsoft/azure-devops-skills (55 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 1,203 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.