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 wiql-queriesgit 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/wiql-queries)<a href="https://agentmods.dev/skills/joshuaramirez/ms-ado-az-claude-code-plugin/wiql-queries"><img src="https://agentmods.dev/badge/skills/joshuaramirez/ms-ado-az-claude-code-plugin/wiql-queries/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/joshuaramirez/ms-ado-az-claude-code-plugin/wiql-queries"><img src="https://agentmods.dev/badge/skills/joshuaramirez/ms-ado-az-claude-code-plugin/wiql-queries.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.00093 | $0.01766 |
| Opus 5 | $0.00046 | $0.00883 |
| Sonnet 5 | $0.00019 | $0.00353 |
| Haiku 4.5 | $0.00009 | $0.00177 |
Grade A, and why
wiql-queries 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 10d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WIQL Query Reference (Verified)
CRITICAL LIMITATIONS - READ FIRST
-
NO TOP CLAUSE - WIQL does NOT support
SELECT TOP Nlike SQL Server. Limit results with shell:az boards query --wiql "..." -o table | head -10 -
Use explicit project name - The
@projectmacro is unreliable in CLI:-- UNRELIABLE: WHERE [System.TeamProject] = @project -- RELIABLE: WHERE [System.TeamProject] = 'YourProjectName' -
Only flat queries supported - The CLI only supports flat queries, not tree/hierarchical queries.
-
NO LIKE OPERATOR - WIQL does NOT support SQL-style LIKE patterns. Use CONTAINS instead:
-- DOES NOT WORK: WHERE [System.Title] LIKE '%keyword%' -- USE THIS INSTEAD: WHERE [System.Title] CONTAINS 'keyword' -
CANNOT ORDER BY System.Parent - Sorting by parent ID is not supported:
-- DOES NOT WORK: ORDER BY [System.Parent] -- WORKAROUND: Filter by parent IDs with IN clause, sort client-side WHERE [System.Parent] IN (1234, 1235, 1236) ORDER BY [System.Id]
Basic Query Syntax
az boards query --wiql "SELECT [fields] FROM workitems WHERE [conditions]" -o table
Verified Working Examples
Query all work items in project
az boards query --wiql "SELECT [System.Id], [System.Title], [System.State] FROM workitems WHERE [System.TeamProject] = 'ProjectName'" -o table
Query by state
az boards query --wiql "SELECT [System.Id], [System.Title] FROM workitems WHERE [System.State] = 'In Progress' AND [System.TeamProject] = 'ProjectName'" -o table
Query by work item type
az boards query --wiql "SELECT [System.Id], [System.Title], [System.State] FROM workitems WHERE [System.WorkItemType] = 'Bug' AND [System.TeamProject] = 'ProjectName'" -o table
Query by assignee
az boards query --wiql "SELECT [System.Id], [System.Title] FROM workitems WHERE [System.AssignedTo] = '[email protected]' AND [System.TeamProject] = 'ProjectName'" -o table
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.
- 10d ago First seen · 172 lines · 93 tokens per session scan A 6611e9f8c6b5
wiql-queries is a skill published in the GitHub repository JoshuaRamirez/ms-ado-az-claude-code-plugin (5 stars, last pushed 6d ago), licensed MIT. It adds 93 tokens to every session and 1,766 once invoked, about $0.0005 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.
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.
remove
Remove a deployed framework or addon from the current workspace.