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/setupgit 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.02949 |
| Opus 5 | $0.00005 | $0.01474 |
| Sonnet 5 | $0.00002 | $0.00590 |
| Haiku 4.5 | $0.00001 | $0.00295 |
Grade D, and why
setup scanned grade D with 3 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 yesterday.
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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash How it starts
The opening of the file, as written. The whole thing — 492 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Setup Command
Guide the user through setting up and configuring the Azure MCP server for Claude Code.
Steps
1. Detect Shell Environment
First, detect what shell environment is being used:
uname -a
Interpret the output:
- MINGW64 or MSYS = Git Bash on Windows
- Linux with "microsoft" or "WSL" in kernel = WSL on Windows
- Darwin = macOS
- Linux (other) = Native Linux
Store this context for providing appropriate instructions throughout setup.
2. Check Node.js
node --version
If Node.js is not installed:
- Inform user Node.js is required for Azure MCP server
- Download from https://nodejs.org/ (recommend LTS version)
- Wait for user to install before proceeding
3. Check Azure CLI Availability
This is the critical step that requires platform-specific handling.
Step 3a: Check if az is in PATH
az version 2>&1
If this succeeds, proceed to Step 4.
Step 3b: If az not found on Git Bash (MINGW64)
When running on Git Bash but az command fails, check if Azure CLI is installed on Windows:
# Check common Windows installation paths
ls "/c/Program Files/Microsoft SDKs/Azure/CLI2/wbin/az.cmd" 2>/dev/null
If found (installed on Windows but not in Git Bash PATH):
Present the user with options using AskUserQuestion:
Option 1: Add to PATH (Recommended) Explain this adds Azure CLI to Git Bash permanently:
echo 'export PATH="$PATH:/c/Program Files/Microsoft SDKs/Azure/CLI2/wbin"' >> ~/.bashrc
source ~/.bashrc
Option 2: Use full path Can invoke az using the full path:
"/c/Program Files/Microsoft SDKs/Azure/CLI2/wbin/az.cmd" version
After user chooses and applies fix, verify az version works.
Step 3c: If Azure CLI not installed anywhere
Check for Azure Developer CLI (azd) as alternative:
azd version 2>&1
Present options to user using AskUserQuestion:
Azure CLI (az) is not installed. Choose how to proceed:
Option 1: Install Azure CLI (Recommended)
- Provides full Azure management capabilities
- Required for Azure MCP server
- Installation requires admin approval (UAC prompt on Windows)
Option 2: Skip for now
- Can still use Azure skills for guidance
- MCP tools won't be available until az is installed
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.
- yesterday First seen · 492 lines · 10 tokens per session scan D eda882ef6a48
setup 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 2,949 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, downloads and executes remote code, makes network calls). 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.