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 JoshuaRamirez/ms-ado-az-claude-code-plugin --skill work-item-fieldsgit clone --depth 1 https://github.com/JoshuaRamirez/ms-ado-az-claude-code-pluginWrote 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/joshuaramirez/ms-ado-az-claude-code-plugin/work-item-fields)<a href="https://agentmods.dev/skills/joshuaramirez/ms-ado-az-claude-code-plugin/work-item-fields"><img src="https://agentmods.dev/badge/skills/joshuaramirez/ms-ado-az-claude-code-plugin/work-item-fields.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.00087 | $0.01599 |
| Opus 5 | $0.00044 | $0.00800 |
| Sonnet 5 | $0.00017 | $0.00320 |
| Haiku 4.5 | $0.00009 | $0.00160 |
Grade A, and why
work-item-fields 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure DevOps Work Item Fields Reference (Verified)
System Fields (All Work Item Types)
| Display Name | Reference Name | Type | Description |
|---|---|---|---|
| ID | System.Id | Integer | Unique identifier |
| Title | System.Title | String | Work item title |
| State | System.State | String | Current state |
| Reason | System.Reason | String | Reason for state |
| Work Item Type | System.WorkItemType | String | Bug, Task, etc. |
| Assigned To | System.AssignedTo | Identity | Person assigned |
| Created By | System.CreatedBy | Identity | Creator |
| Created Date | System.CreatedDate | DateTime | Creation timestamp |
| Changed By | System.ChangedBy | Identity | Last modifier |
| Changed Date | System.ChangedDate | DateTime | Last modified |
| Area Path | System.AreaPath | TreePath | Area classification |
| Iteration Path | System.IterationPath | TreePath | Sprint/iteration |
| Tags | System.Tags | String | Semicolon-separated |
| Description | System.Description | HTML | Rich text description |
| History | System.History | HTML | Discussion entry |
| Rev | System.Rev | Integer | Revision number |
| Board Column | System.BoardColumn | String | Kanban column |
| Board Lane | System.BoardLane | String | Swimlane |
Common Fields by Category
Scheduling
| Display Name | Reference Name | Type |
|---|---|---|
| Story Points | Microsoft.VSTS.Scheduling.StoryPoints | Double |
| Effort | Microsoft.VSTS.Scheduling.Effort | Double |
| Original Estimate | Microsoft.VSTS.Scheduling.OriginalEstimate | Double |
| Remaining Work | Microsoft.VSTS.Scheduling.RemainingWork | Double |
| Completed Work | Microsoft.VSTS.Scheduling.CompletedWork | Double |
| Start Date | Microsoft.VSTS.Scheduling.StartDate | DateTime |
| Finish Date | Microsoft.VSTS.Scheduling.FinishDate | DateTime |
Priority & Severity
| Display Name | Reference Name | Values |
|---|---|---|
| Priority | Microsoft.VSTS.Common.Priority | 1, 2, 3, 4 |
| Severity | Microsoft.VSTS.Common.Severity | 1 - Critical, 2 - High, 3 - Medium, 4 - Low |
| Value Area | Microsoft.VSTS.Common.ValueArea | Business, Architectural |
| Risk | Microsoft.VSTS.Common.Risk | 1 - High, 2 - Medium, 3 - Low |
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 · 157 lines · 87 tokens per session scan A 8ef8f8948665
work-item-fields is a skill published in the GitHub repository JoshuaRamirez/ms-ado-az-claude-code-plugin (5 stars, last pushed 4d ago), licensed MIT. It adds 87 tokens to every session and 1,599 once invoked, about $0.0004 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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.