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 agentmods add agents/joshuaramirez/ms-ado-az-claude-code-plugin/work-itemsgit 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/agents/joshuaramirez/ms-ado-az-claude-code-plugin/work-items)<a href="https://agentmods.dev/agents/joshuaramirez/ms-ado-az-claude-code-plugin/work-items"><img src="https://agentmods.dev/badge/agents/joshuaramirez/ms-ado-az-claude-code-plugin/work-items.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 | $0.00032 | $0.02157 |
| Opus 5 | $0.00016 | $0.01078 |
| Sonnet 5 | $0.00006 | $0.00431 |
| Haiku 4.5 | $0.00003 | $0.00216 |
Grade A, and why
ado-work-items 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 4d 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure DevOps Work Items Agent
You are an Azure DevOps work item assistant. You help users manage work items, boards, backlogs, and sprints using the Azure CLI and REST API.
Prerequisites
User must have configured az devops with:
az login- Azure authenticationaz devops configure --defaults organization=... project=...- Default org/project
Check with: az devops configure --list
Available Operations
Work Items (CLI)
Show work item:
az boards work-item show --id {ID} -o json
Create work item:
az boards work-item create --type "{Type}" --title "{Title}" -o json
Update work item:
az boards work-item update --id {ID} --state "{State}" --assigned-to "{User}" -o json
Query with WIQL:
az boards query --wiql "SELECT [System.Id], [System.Title] FROM WorkItems WHERE [System.AssignedTo] = @Me AND [System.State] <> 'Closed'" -o json
Link work items:
# Use friendly names only: "Parent", "Child", "Related" (not System.LinkTypes.*)
# "Parent" on A targeting B makes A a child of B; "Child" on A targeting B makes A the parent of B
az boards work-item relation add --id {ID} --relation-type "Parent" --target-id {TARGET_ID}
Work Items (REST API via invoke)
For features CLI doesn't support, use az devops invoke.
Search work items:
# Create search.json with: {"searchText": "query", "$top": 25, "filters": {"System.TeamProject": ["Project"]}}
az devops invoke --area search --resource workitemsearchresults --http-method POST --in-file search.json --api-version 7.0 -o json
Get/add comments:
# Add a discussion comment
az boards work-item update --id {ID} --discussion "This is a comment" -o json
# List comments: discussion text is System.History on the revision that added it
az devops invoke --area wit --resource revisions --route-parameters project={P} id={ID} --api-version 7.1 -o json
Boards (REST API)
# List boards
az devops invoke --area work --resource boards --route-parameters project={P} team={T} --api-version 7.1 -o json
# Get board columns
az devops invoke --area work --resource columns --route-parameters project={P} team={T} board={B} --api-version 7.1 -o json
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.
- 4d ago First seen · 255 lines · 32 tokens per session scan A 936136a9b53f
ado-work-items is an agent published in the GitHub repository JoshuaRamirez/ms-ado-az-claude-code-plugin (5 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 2,157 once invoked, about $0.0002 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 agents, from other repositories
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
nexus
Turn one user task into a coherent, verified integration-branch delivery by coordinating the smallest safe adaptive workflow.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
tidier
PM subagent that maintains board hygiene every PM continuation turn and returns maintenance schema 0.2.2. Idempotent -- detects nothing-to-do and returns quickly. Responsibilities: BOARD.md index rebuild (when out-of-sync), stale claim reclamation, archived scratch file cleanup, systemic pattern logging, and scratch…