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 jonathan-vella/apex-accelerator --skill apex-azure-resourcesgit clone --depth 1 https://github.com/jonathan-vella/apex-acceleratorWrote 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/jonathan-vella/apex-accelerator/apex-azure-resources)<a href="https://agentmods.dev/skills/jonathan-vella/apex-accelerator/apex-azure-resources"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/apex-azure-resources/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/jonathan-vella/apex-accelerator/apex-azure-resources"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/apex-azure-resources.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.00110 | $0.01682 |
| Opus 5.5 | $0.00044 | $0.00673 |
| Sonnet 5.5 | $0.00022 | $0.00336 |
| Haiku 4.5 | $0.00011 | $0.00168 |
Grade A, and why
apex-azure-resources 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 22d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Resources
Discover, inventory, and visualize existing Azure resources. Combines two related capabilities:
- Lookup mode — query and list resources (single type or cross-cutting via
Azure Resource Graph). Replaces the legacy
azure-resource-lookupskill. - Visualize mode — analyze a resource group and generate a detailed Mermaid
architecture diagram. Replaces the legacy
azure-resource-visualizerskill.
Both modes share references/azure-resource-graph.md for KQL patterns.
Prerequisites
Confirm authorized subscription IDs and read access. Use installed Azure CLI with Resource Graph support or an available MCP tool; tool names below are routing hints, not proof of runtime availability. Installation requires authorization.
Mode A: Lookup
Use this mode when the user wants to list / find / show Azure resources.
When to Use Lookup
- List resources of any type (VMs, web apps, storage accounts, container apps, databases, etc.)
- Show resources in a specific subscription or resource group
- Query resources across multiple subscriptions or resource types
- Find orphaned resources (unattached disks, unused NICs, idle IPs)
- Discover resources missing required tags or configurations
- Get a resource inventory spanning multiple types
- Find resources in a specific state (unhealthy, failed provisioning, stopped)
- Answer "what resources do I have?" or "show me my Azure resources"
- List web apps, websites or App Services — there is no dedicated MCP
listcommand for App Service, so these prompts go to Azure Resource Graph
💡 Tip: For single-resource-type queries, first check if a dedicated MCP tool can handle it (see routing table below). If none exists, use Azure Resource Graph (ARG).
Quick Reference
| Property | Value |
|---|---|
| Query Language | KQL (Kusto Query Language subset) |
| CLI Command | az graph query -q "<KQL>" -o table |
| Extension | az extension add --name resource-graph |
| MCP Tool | extension_cli_generate with intent for az graph query |
| Best For | Cross-subscription queries, orphaned resources, tag audits |
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 22d ago Changed · +4 lines 1c08ebfa9994
- 23d ago First seen · 136 lines · 110 tokens per session scan A a4c83f270cdf
apex-azure-resources is a skill published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed yesterday), licensed MIT. It adds 110 tokens to every session and 1,682 once invoked, about $0.0004 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-23.
Other skills, from other repositories
chaos-experiment
Design and document chaos engineering experiments. Guide steady state baseline, hypothesis formation, failure injection plans, and results analysis. Use when you say "design a chaos experiment", "plan a game day", "failure injection", "test resilience", or "chaos engineering". Do NOT use for security threat analysis…
infrastructure-as-code
Domain: DevOps & Cloud Engineering.
cloud-solution-architect
Design well-architected Azure cloud systems — 10 design principles, 6 architecture styles, 44 design patterns, technology choices, WAF pillars.
bicep-avm-mastery
Azure Verified Modules (AVM), Bicep best practices, and MCP-powered infrastructure as code for Azure.
foundry-agent-platform
Microsoft Foundry agent deployment, orchestration, and cloud-native AI service patterns.
sse-streaming
POST-based Server-Sent Events streaming for Azure Functions — HTTP streaming, chunked response parsing, reconnection.