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.
git clone --depth 1 https://github.com/jnPiyush/AgentXWrote 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/commands/jnpiyush/agentx/ado-add-work-item)<a href="https://agentmods.dev/commands/jnpiyush/agentx/ado-add-work-item"><img src="https://agentmods.dev/badge/commands/jnpiyush/agentx/ado-add-work-item/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/commands/jnpiyush/agentx/ado-add-work-item"><img src="https://agentmods.dev/badge/commands/jnpiyush/agentx/ado-add-work-item.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.00026 | $0.00186 |
| Opus 5.5 | $0.00010 | $0.00074 |
| Sonnet 5.5 | $0.00005 | $0.00037 |
| Haiku 4.5 | $0.00003 | $0.00019 |
Grade A, and why
ADO: Add Single Work Item 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.
What it actually says
Create one Azure DevOps work item based on the user description.
Use interaction templates from #file:.github/instructions/ado/ado-interaction-templates.instructions.md to compose the description and acceptance criteria.
- Identify the work item type from the user request (Bug, User Story, Task, etc.).
- Confirm or detect the ADO project and process template.
- Check for existing duplicates using the Azure CLI or WIQL-backed discovery flow.
- If no duplicates found, compose field values using the appropriate A-series template.
- Apply content format detection (Markdown vs. HTML).
- Create the item using the Azure CLI-based ADO provider flow.
- Present the new work item ID and URL to the user.
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 · 19 lines · 26 tokens per session scan A 99dab703e937
ADO: Add Single Work Item is a command published in the GitHub repository jnPiyush/AgentX (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 26 tokens to every session and 186 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-09-06.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.