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 G1Joshi/Agent-Skills --skill azurecligit clone --depth 1 https://github.com/G1Joshi/Agent-SkillsWrote 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/g1joshi/agent-skills/azurecli)<a href="https://agentmods.dev/skills/g1joshi/agent-skills/azurecli"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/azurecli.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.00014 | $0.00361 |
| Opus 5 | $0.00007 | $0.00180 |
| Sonnet 5 | $0.00003 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
azurecli 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 4d 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
Azure CLI (az)
The Azure CLI is the standard tool for managing Azure resources. 2025 brings deeper integration with Bicep (Azure's IaC language) and AI assistance.
When to Use
- Management: Quickly creating Resource Groups or AKS clusters.
- Automation: CI/CD pipelines targeting Azure.
- Querying: Using JMESPath to find resources.
Quick Start
# Login
az login
# Set Subscription
az account set --subscription "My Subscription"
# Create AKS Cluster
az aks create --resource-group myResourceGroup --name myAKSCluster --node-count 1 --generate-ssh-keys
Core Concepts
Command Groups
Hierarchical structure: az group, az vm, az network.
Interactive Mode
az interactive. Provides auto-completion, examples, and descriptions in the terminal.
Extensions
The CLI is extensible.
az extension add --name aks-preview
Best Practices (2025)
Do:
- Use
az upgrade: Keep the CLI and extensions auto-updated. - Use Managed Identity: When running on Azure VMs/Functions, use
az login --identityto avoid credentials. - Use
--no-wait: For long operations (creating VMs), fire and forget.
Don't:
- Don't hardcode Service Principals: Use Workload Identity Federation (OIDC) in GitHub Actions instead of secrets.
References
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.
- 4d ago First seen · 59 lines · 14 tokens per session scan A f64197e909ed
azurecli is a skill published in the GitHub repository G1Joshi/Agent-Skills (12 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 361 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-09-03.
Other skills, from other repositories
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
shipping-and-launch
Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
tdd-configure-ci
Configures CI/CD pipelines to mechanically enforce CONSTRAINTS.md quality bars and Floor-Guard anti-cheat rules. (Optional Utility).
nx-ci-monitor
Monitor Nx Cloud CI pipeline status and handle self-healing fixes automatically. Use when user says "watch CI", "monitor pipeline", "check CI status", "fix CI failures", or "self-heal CI". Requires Nx Cloud connection. Do NOT use for local task execution (use nx-run-tasks) or general CI debugging outside Nx Cloud.
aws-advisor
Expert AWS Cloud Advisor for architecture design, security review, and implementation guidance. Leverages AWS MCP tools for accurate, documentation-backed answers. Use when user asks about AWS architecture, security, service selection, migrations, troubleshooting, or learning AWS. Triggers on AWS, Lambda, S3, EC2…
netlify-deploy
Deploy web projects to Netlify using the Netlify CLI (npx netlify). Use when the user asks to deploy, host, publish, or link a site/repo on Netlify, including preview and production deploys. Do NOT use for deploying to Vercel, Cloudflare, or Render (use their respective skills).