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/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/g1joshi/agent-skills/azurecli"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/azurecli.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.00038 | $0.00997 |
| Opus 5.5 | $0.00015 | $0.00399 |
| Sonnet 5.5 | $0.00008 | $0.00199 |
| Haiku 4.5 | $0.00004 | $0.00100 |
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 26d 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 CLI (az)
The Azure CLI provides cross-platform command-line management for Azure infrastructure, featuring tight integration with Bicep templates and automated cloud provisioning.
When to Use
- Automating Azure Cloud Operations: Scripting resource deployment, role assignments, and monitoring via
az. - CI/CD Azure DevOps & GitHub Actions: Deploying infrastructure and applications using service principals or OIDC.
- JMESPath Querying of Azure Resources: Extracting specific cloud parameters using
--query. - Container Registry & AKS Cluster Management: Authenticating Docker clients and managing Kubernetes credentials.
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
Resource Group Creation & Infrastructure Deployment
Deploying resources with Bicep / ARM templates:
# Set default subscription and location
az account set --subscription "Production-Subscription"
az configure --defaults location=eastus
# Create Resource Group
az group create --name rg-production-platform --location eastus
# Deploy infrastructure via Bicep template
az deployment group create \
--resource-group rg-production-platform \
--template-file main.bicep \
--parameters environment=prod [email protected]
Querying and Filtering with JMESPath (--query)
Extracting resource properties without installing jq:
# List all running VMs with their private IPs and OS type
az vm list \
--show-details \
--query "[?powerState=='VM running'].{Name:name, IP:privateIps, OS:osType, Size:hardwareProfile.vmSize}" \
--output table
# Get public IP address of an Application Gateway
APP_GATEWAY_IP=$(az network public-ip show \
--resource-group rg-production-platform \
--name pip-appgw \
--query ipAddress \
--output tsv)
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.
- 26d ago Changed · +5 lines 07820d67948d
- 1mo ago Changed · +67 lines · +24 tokens per session 961428a91a33
- 1mo ago First seen · 59 lines · 14 tokens per session scan A f64197e909ed
azurecli is a skill published in the GitHub repository G1Joshi/Agent-Skills (15 stars, last pushed 26d ago), licensed MIT. It adds 38 tokens to every session and 997 once invoked, about $0.0002 per session on Opus 5.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, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
ci-cd-pipelines
Automated quality gates from commit to production. Every merge to main is potentially shippable. No manual steps in the deployment path.
ci-cd-and-automation
Guidance for setting up continuous integration and delivery, where automated checks test and prepare software changes before release.
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.
cost-optimization
Guides systematic cloud and infrastructure cost reduction. Use when cloud bills are growing unpredictably, when rightsizing resources, when evaluating reserved capacity, or when building cost-aware architecture. Use when you need to optimize spend without sacrificing reliability or performance.