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 commands/joshuaramirez/ms-ado-az-claude-code-plugin/statusgit 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/commands/joshuaramirez/ms-ado-az-claude-code-plugin/status)<a href="https://agentmods.dev/commands/joshuaramirez/ms-ado-az-claude-code-plugin/status"><img src="https://agentmods.dev/badge/commands/joshuaramirez/ms-ado-az-claude-code-plugin/status.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.00009 | $0.00781 |
| Opus 5 | $0.00005 | $0.00391 |
| Sonnet 5 | $0.00002 | $0.00156 |
| Haiku 4.5 | $0.00001 | $0.00078 |
Grade A, and why
status 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 6d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure DevOps Status Check
Check the current Azure DevOps CLI configuration and verify connectivity.
Step 1: Check Azure CLI Version
Verify Azure CLI is installed:
az --version
Look for the version number. If this fails, Azure CLI is not installed or not in PATH.
Step 2: Check DevOps Extension
Verify the azure-devops extension is installed:
az extension list --query "[?name=='azure-devops'].{name:name, version:version}" -o table
If empty, the extension needs to be installed with az extension add --name azure-devops.
Step 3: Show Current Configuration
Display the current default organization and project:
az devops configure --list
Expected output shows:
- organization: Your Azure DevOps organization URL (e.g.,
https://dev.azure.com/yourorg) - project: Your default project name
If either is blank, run /ado:setup to configure.
Step 4: Test Connectivity
Read the configured project from Step 3 (az devops configure --list). If project is blank, report connectivity FAILED and tell the user to run /ado:setup.
Otherwise run a live project lookup to verify authentication and access:
az devops project show --project {PROJECT}
If this succeeds, the configuration is working. This check works even when the project has no work items.
Interpreting Results
All Green
If all checks pass:
- Azure CLI is installed
- DevOps extension is present
- Organization and project are configured
- Connectivity and authentication are working
Report: "Azure DevOps CLI is configured and working correctly."
Common Issues
Azure CLI not found:
- Error:
'az' is not recognizedoraz: command not found - Fix: Install Azure CLI (see README for instructions)
Extension not installed:
- Extension list is empty
- Fix: Run
az extension add --name azure-devops
No defaults configured:
- Organization or project is blank
- Fix: Run
/ado:setuporaz devops configure --defaults organization=URL project=NAME
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.
- 6d ago First seen · 131 lines · 9 tokens per session scan A babc81f383b4
status is a command published in the GitHub repository JoshuaRamirez/ms-ado-az-claude-code-plugin (5 stars, last pushed 2d ago), licensed MIT. It adds 9 tokens to every session and 781 once invoked, about $0.0000 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.