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/charris-msft/azure-plugin/statusgit clone --depth 1 https://github.com/charris-msft/azure-pluginWhat 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.00010 | $0.00790 |
| Opus 5 | $0.00005 | $0.00395 |
| Sonnet 5 | $0.00002 | $0.00158 |
| Haiku 4.5 | $0.00001 | $0.00079 |
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 2d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Status Command
Check the status of Azure MCP server and display available capabilities.
Status Checks
1. Azure CLI Status
Check Azure CLI installation and authentication:
# Version
az version --output json 2>&1
# Current account
az account show --query "{Name:name, ID:id, TenantId:tenantId}" -o json 2>&1
Report:
- CLI version
- Logged in user/service principal
- Current subscription
- Tenant ID
2. Azure MCP Server Status
Attempt to use an MCP tool to verify the server is running:
Use azure_subscription_list to:
- Confirm MCP server is responsive
- Verify authentication is working
- Get subscription count
If MCP tools are not available:
- Inform user the Azure MCP server is not enabled
- Direct them to
/mcpto enable it - Or run
/azure:setupfor guided configuration
3. Available MCP Tools
List the major tool categories available:
| Category | Tools | Description |
|---|---|---|
| Subscription | azure_subscription_list |
List subscriptions |
| Resource Groups | azure_resource_group_list |
List resource groups |
| Storage | azure_storage_* |
Storage operations |
| Compute | azure_appservice_*, azure_aks_* |
Compute services |
| Data | azure_sql_*, azure_cosmosdb_* |
Database services |
| Security | azure_keyvault_*, azure_rbac_* |
Security services |
| AI | azure_search_*, azure_speech_* |
AI services |
| CLI | azure_cli_generate |
Generate CLI commands |
4. Quick Health Check
If MCP is enabled, perform quick validation:
- Subscription access: List subscriptions
- Resource access: List resource groups (if subscription selected)
- Tool availability: Confirm tools respond
Output Format
Display a comprehensive status report:
Azure MCP Status
================
Azure CLI
Version: 2.x.x
Status: ✓ Installed
Authentication
User: [email protected]
Type: Interactive
Status: ✓ Authenticated
Subscription
Name: Contoso Production
ID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
State: Enabled
Azure MCP Server
Status: ✓ Running
Tools Available: 40+
Quick Test Results
Subscriptions: ✓ 3 found
Resource Groups: ✓ 15 found
Ready to use Azure tools!
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.
- 2d ago First seen · 146 lines · 10 tokens per session scan A 5642a6c3891d
status is a command published in the GitHub repository charris-msft/azure-plugin (2 stars, last pushed 7mo ago), licensed MIT. It adds 10 tokens to every session and 790 once invoked, about $0.0001 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
git
Git operations with intelligent commit messages and workflow optimization.
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.