Azure Prices Agent Skill
Look up and compare Azure service pricing using the Azure Retail Prices API. Use this skill whenever the user asks about Azure costs, pricing, rates, or wants to compare prices across regions or services — even if they don't say "pricing" explicitly. Trigger for questions like "how much does a D2 v2 VM cost?", "cheapest region for Azure SQL", or "compare storage prices between eastus and westeurope".
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/Code-and-Sorts/awesome-copilot-agents --skill azure-pricesThe instruction itself
10 sections, as written by the authorAzure Prices
Fetch and compare live Azure service pricing using the bundled scripts that call the Azure Retail Prices API.
Execution Rules
Always use the bundled npm script for price lookups and comparisons when terminal execution is available.
DO NOT call the Azure Retail Prices API directly. You can only use the script to call the API.
Scripts
All scripts live in ./scripts/ and run via npm:
# List sample service names (discover what's available)
npm run --prefix ./scripts get-prices
# Get prices for a service in a region (default region: eastus)
npm run --prefix ./scripts get-prices -- "Virtual Machines" eastus
The script accepts two positional arguments:
- Service name (required for price lookup) — e.g.
"Virtual Machines","SQL Database","Storage","Azure Cosmos DB" - Region (optional, defaults to
eastus) — e.g.eastus,westus2,westeurope,southeastasia
When called with no arguments, it prints a sample of available service names.
How to Use
The npm commands below are the preferred execution path for this skill and should be used instead of direct API calls whenever command execution is available.
Single region lookup
Run the script with the service name and region. Present results in a readable table.
Cross-region comparison
To compare prices across regions, run the script multiple times — once per region — then combine the results into a comparison table. For example, to compare Virtual Machines prices across three regions:
npm run --prefix ./scripts get-prices -- "Virtual Machines" eastus
npm run --prefix ./scripts get-prices -- "Virtual Machines" westus2
npm run --prefix ./scripts get-prices -- "Virtual Machines" westeurope
Then join the results by SKU name to show a side-by-side comparison table with columns for each region.
Finding the cheapest region
Run prices for the target service across several common regions and sort by price. Common Azure regions to compare:
eastus,eastus2,westus2,centralus(US)westeurope,northeurope,uksouth(Europe)southeastasia,eastasia,japaneast(Asia-Pacific)
Service discovery
If the user isn't sure of the exact service name, run the script with no arguments first to get a sample of available names, then use the closest match.
Fallback Behavior
If command execution is unavailable, use the local script implementation as the behavioral reference, then fall back to public pricing sources only as needed. In that case, explicitly tell the user that script execution was unavailable before presenting results.
Output Format
Present pricing results as markdown tables. For comparisons, use a format like:
| SKU | East US | West US 2 | West Europe |
|-----|---------|-----------|-------------|
| D2 v2 | $0.10/hr | $0.11/hr | $0.12/hr |
| D4 v2 | $0.20/hr | $0.22/hr | $0.24/hr |
Highlight the cheapest option per row when doing comparisons. Include the currency and unit of measure.
Other skills for the same job
different authors, same section of the catalogue
Assess Kubernetes workloads and cluster configuration for AKS Automatic compatibility. Identifies incompatibilities, generates fixes, and guides migration from AKS Standard to AKS Automatic. WHEN: migrate to AKS Automatic, check AKS Automatic readiness, validate manifests for Automatic, assess cluster for Automatic compatibility, fix deployment for Automatic compatibility, identify AKS Automatic migration blockers, is my cluster ready for AKS Automatic.
Discovers available Azure OpenAI model capacity across regions and projects. Analyzes quota limits, compares availability, and recommends optimal deployment locations based on capacity requirements. USE FOR: find capacity, check quota, where can I deploy, capacity discovery, best region for capacity, multi-project capacity search, quota analysis, model availability, region comparison, check TPM availability. DO NOT USE FOR: actual deployment (hand off to preset or customize after discovery), quota increase requests (direct user to Azure Portal), listing existing deployments.
Interactive guided deployment flow for Azure OpenAI models with full customization control. Step-by-step selection of model version, SKU (GlobalStandard/Standard/ProvisionedManaged), capacity, RAI policy (content filter), and advanced options (dynamic quota, priority processing, spillover). USE FOR: custom deployment, customize model deployment, choose version, select SKU, set capacity, configure content filter, RAI policy, deployment options, detailed deployment, advanced deployment, PTU deployment, provisioned throughput. DO NOT USE FOR: quick deployment to optimal region (use preset).
Unified Azure OpenAI model deployment skill with intelligent intent-based routing. Handles quick preset deployments, fully customized deployments (version/SKU/capacity/RAI policy), and capacity discovery across regions and projects. USE FOR: deploy model, deploy gpt, create deployment, model deployment, deploy openai model, set up model, provision model, find capacity, check model availability, where can I deploy, best region for model, capacity analysis. DO NOT USE FOR: listing existing deployments (use foundry_models_deployments_list MCP tool), deleting deployments, agent creation (use agent/create), project creation (use project/create).
Intelligently deploys Azure OpenAI models to optimal regions by analyzing capacity across all available regions. Automatically checks current region first and shows alternatives if needed. USE FOR: quick deployment, optimal region, best region, automatic region selection, fast setup, multi-region capacity check, high availability deployment, deploy to best location. DO NOT USE FOR: custom SKU selection (use customize), specific version selection (use customize), custom capacity configuration (use customize), PTU deployments (use customize).
This skill should be used when working with LaminDB, an open-source data framework for biology that makes data queryable, traceable, reproducible, and FAIR. Use when managing biological datasets (scRNA-seq, spatial, flow cytometry, etc.), tracking computational workflows, curating and validating data with biological ontologies, building data lakehouses, or ensuring data lineage and reproducibility in biological research. Covers data management, annotation, ontologies (genes, cell types, diseases, tissues), schema validation, integrations with workflow managers (Nextflow, Snakemake) and MLOps platforms (W&B, MLflow), and deployment strategies.
Latch platform for bioinformatics workflows. Build pipelines with Latch SDK, @workflow/@task decorators, deploy serverless workflows, LatchFile/LatchDir, Nextflow/Snakemake integration.
Run Python code in the cloud with serverless containers, GPUs, and autoscaling. Use when deploying ML models, running batch processing jobs, scheduling compute-intensive tasks, or serving APIs that require GPU acceleration or dynamic scaling.
How to use it
Take code-and-sorts/azure-prices from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.