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 amir0135/github-copilot-use-cases --skill azure-resource-visualizergit clone --depth 1 https://github.com/amir0135/github-copilot-use-casesWrote 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/amir0135/github-copilot-use-cases/azure-resource-visualizer)<a href="https://agentmods.dev/skills/amir0135/github-copilot-use-cases/azure-resource-visualizer"><img src="https://agentmods.dev/badge/skills/amir0135/github-copilot-use-cases/azure-resource-visualizer/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/amir0135/github-copilot-use-cases/azure-resource-visualizer"><img src="https://agentmods.dev/badge/skills/amir0135/github-copilot-use-cases/azure-resource-visualizer.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.00049 | $0.02165 |
| Opus 5.5 | $0.00020 | $0.00866 |
| Sonnet 5.5 | $0.00010 | $0.00433 |
| Haiku 4.5 | $0.00005 | $0.00216 |
Grade A, and why
azure-resource-visualizer 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 1mo 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.
This is a copy
83% identical to azure-resource-visualizer — 71 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Resource Visualizer - Architecture Diagram Generator
A user may ask for help understanding how individual resources fit together, or to create a diagram showing their relationships. Your mission is to examine Azure resource groups, understand their structure and relationships, and generate comprehensive Mermaid diagrams that clearly illustrate the architecture.
Core Responsibilities
- Resource Group Discovery: List available resource groups when not specified
- Deep Resource Analysis: Examine all resources, their configurations, and interdependencies
- Relationship Mapping: Identify and document all connections between resources
- Diagram Generation: Create detailed, accurate Mermaid diagrams
- Documentation Creation: Produce clear markdown files with embedded diagrams
Workflow Process
Step 1: Resource Group Selection
If the user hasn't specified a resource group:
- Use your tools to query available resource groups. If you do not have a tool for this, use
az. - Present a numbered list of resource groups with their locations
- Ask the user to select one by number or name
- Wait for user response before proceeding
If a resource group is specified, validate it exists and proceed.
Step 2: Resource Discovery & Analysis
Once you have the resource group:
-
Query all resources in the resource group using Azure MCP tools or
az. -
Analyze each resource type and capture:
- Resource name and type
- SKU/tier information
- Location/region
- Key configuration properties
- Network settings (VNets, subnets, private endpoints)
- Identity and access (Managed Identity, RBAC)
- Dependencies and connections
-
Map relationships by identifying:
- Network connections: VNet peering, subnet assignments, NSG rules, private endpoints
- Data flow: Apps → Databases, Functions → Storage, API Management → Backends
- Identity: Managed identities connecting to resources
- Configuration: App Settings pointing to Key Vaults, connection strings
- Dependencies: Parent-child relationships, required resources
What ships with it
1 file 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.
- 1mo ago First seen · 233 lines · 49 tokens per session scan A 2e4a19cefbd4
azure-resource-visualizer is a skill published in the GitHub repository amir0135/github-copilot-use-cases (2 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 2,165 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 83% identical to azure-resource-visualizer, differing in 71 lines, and is treated as a copy.
Other skills, from other repositories
architecture-diagram
WHAT — Create polished dark-themed architecture diagrams as self-contained HTML+SVG files (inline SVG, CSS styling, PNG/PDF export toolbar). Use when the user asks for system, infrastructure, cloud, security, or network topology diagrams rendered as a shareable visual artifact rather than code.
aria-input-field-name
Use when applies to all (except type=hidden), , , and custom form widgets using role=textbox, role=combobox, role=spinbutton, role=searchbox, or role=listbox.
aria-treeitem-name
Use when applies to custom tree widgets built with role='tree', role='treeitem', and role='group'. Common in file explorers, nested navigation menus, org charts, and any UI where items can be expanded or collapsed to reveal children.
color-contrast
Use when applies to all visible text and text images, UI component borders (input fields, buttons), focus indicators, icons that convey meaning, and graphical objects required to understand content. Does not apply to inactive/disabled UI components or purely decorative elements.
button-name
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Provide accessible names for buttons. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
css-custom-properties
Use when reviewing stylesheets, component styles, and responsive behavior related to Use CSS custom properties for design tokens. Check the rendered layout across breakpoints and interaction states before proposing a fix.