VisioIntegration: Skill for Claude Code

.github/skills/azure-diagram-authoring/SKILL.md

azure-diagram-authoring is a skill for Claude Code, Codex from CloudDaddyZA/VisioIntegration. It costs 77 tokens per session (874 once invoked), scanned A, original, MIT.

Guidance for creating Azure architecture diagrams with the Visio MCP server. Azure is Microsoft's cloud platform, and an architecture diagram shows how its services and boundaries fit together.

In plain words
What is it for?
Use it to create or edit Azure diagrams, apply reference architectures, validate designs, and export them as Visio, draw.io, or Mermaid files.
Why use it?
It provides a consistent way to build, check, import, and export diagrams while considering Azure design frameworks.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is CloudDaddyZA/VisioIntegration's own configuration. It tells Claude Code and Codex how to work on VisioIntegration itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything VisioIntegration configures →

Reuse

Borrowing it

Nothing to install: this file belongs to CloudDaddyZA/VisioIntegration. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/CloudDaddyZA/VisioIntegration/master/.github/skills/azure-diagram-authoring/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/CloudDaddyZA/VisioIntegration

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for azure-diagram-authoring

README.md
[![agentmods](https://agentmods.dev/badge/skills/clouddaddyza/visiointegration/azure-diagram-authoring/github.svg)](https://agentmods.dev/skills/clouddaddyza/visiointegration/azure-diagram-authoring)
Your own site
<a href="https://agentmods.dev/skills/clouddaddyza/visiointegration/azure-diagram-authoring"><img src="https://agentmods.dev/badge/skills/clouddaddyza/visiointegration/azure-diagram-authoring/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.

agentmods 80×15 button for azure-diagram-authoring

Your own site · 80×15
<a href="https://agentmods.dev/skills/clouddaddyza/visiointegration/azure-diagram-authoring"><img src="https://agentmods.dev/badge/skills/clouddaddyza/visiointegration/azure-diagram-authoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 874 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00077 $0.00874
Opus 5 $0.00039 $0.00437
Sonnet 5 $0.00015 $0.00175
Haiku 4.5 $0.00008 $0.00087

Measured 11d ago against content hash 589d68b21290, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

azure-diagram-authoring 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 11d 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.

.github/skills/azure-diagram-authoring/SKILL.md · 70 lines

How it starts

The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Azure diagram authoring

This skill guides building correct, standards-aligned Azure architecture diagrams using the visio-azure MCP server. It encodes the project's conventions so diagrams come out right the first time.

When to use

Use this skill when the user asks to:

  • Create an Azure architecture diagram from a description or business goal.
  • Apply a built-in reference architecture (e.g. AI Landing Zone, Microservices on AKS).
  • Validate a design against WAF (5 pillars) or CAF (7 principles).
  • Export a diagram to .vsdx (Visio), .drawio (draw.io), or .mmd (Mermaid).
  • Import an existing diagram (.vsdx), a screenshot, or an Azure Pricing Calculator URL.

Prerequisite

The visio-azure MCP server must be connected. A sample config lives at .vscode/mcp.json. If the server's tools are not available, ask the user to add and trust it first.

Authoring workflow

  1. Create the diagram with create_diagram (give it a descriptive name).
  2. Boundaries first. Add containers with add_boundary before resources. Valid boundary types: resource_group, virtual_network, subnet, subscription, region, availability_zone, security_boundary.
  3. Add resources with add_azure_resource. Use canonical resource_type values from the catalog (call list_azure_shapes to browse). Assign each resource to its boundary via group_id so positions auto-calculate.
  4. Connect resources with connect_resources, using labeled connectors that reflect real traffic/data flow.
  5. Lay out with auto_layout (tiered | grid | grouped). Never hardcode coordinates unless replicating a specific reference architecture.
  6. Validate with validate_waf and validate_caf; summarize findings and offer suggest_architecture_improvements.
  7. Save only when asked, via save_diagram (.vsdx, .drawio, or .mmd).

Conventions to enforce

  • Canonical resource types. Prefer catalog names (virtual_machine, app_service, sql_database, kubernetes_service, api_management). Common aliases (vm, aks, apim) are resolved automatically.
  • CAF naming prefixes. vm-, App Services app-, SQL sql-, VNets vnet-, subnets snet-, Key Vault kv-, Storage st, AKS aks-, Container Registry cr.
  • Coordinates are in inches on an 11×8.5 page; let auto_layout and group_id handle placement.
  • properties on add_azure_resource / add_boundary accepts a string, a dict (auto-serialized), or may be omitted.

Read the full file on GitHub · 70 lines

Changes

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.

  1. 11d ago First seen · 70 lines · 77 tokens per session scan A 589d68b21290

Subscribe to this mod's changes

azure-diagram-authoring is a skill published in the GitHub repository CloudDaddyZA/VisioIntegration (2 stars, last pushed 3mo ago), licensed MIT. It adds 77 tokens to every session and 874 once invoked, about $0.0004 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-08-31.

Related

Other skills, from other repositories

drawio-aws

Use when the user asks for an AWS architecture diagram — VPC/networking, event-driven, landing zone, multi-AZ, serverless pipeline, or any diagram built with AWS service icons. Builds with the declarative layout engine using ground-truth mxgraph.aws4 stencils, validates (stencils/colors/nesting/geometry), runs a…

sparklabx/drawio-ai-kit · 94 tokens

drawio-gcp

Use when the user asks for a GCP or Google Cloud architecture diagram — VPC/networking, GKE, Cloud Run, landing zone, multi-region, or any diagram built with GCP service icons. Builds with the declarative layout engine using ground-truth GCP stencils, validates (stencils/colors/nesting/geometry), runs a render-based…

sparklabx/drawio-ai-kit · 95 tokens

drawio-azure

Use when the user asks for an Azure architecture diagram — VNet/networking, App Service, AKS, landing zone, multi-region, or any diagram built with Azure service icons. Builds with the declarative layout engine using ground-truth Azure stencils, validates (stencils/colors/nesting/geometry), runs a render-based vision…

sparklabx/drawio-ai-kit · 89 tokens

drawio-databricks

Use when the user asks for a Databricks lakehouse architecture diagram — medallion architecture (Bronze/Silver/Gold), Delta Lake, Unity Catalog, workspace deployment, data-plane/control-plane, or any diagram built with Databricks icons. Builds with the declarative layout engine using ground-truth stencils, validates…

sparklabx/drawio-ai-kit · 104 tokens

drawio

WORKFLOW SKILL — Generate Azure architecture diagrams in .drawio via simonkurtz-MSFT MCP server (full Azure icon set, batch creation, transactional mode). Covers architecture, dependency, runtime-flow, and as-built diagrams. WHEN: 'draw.io diagram', 'Azure architecture diagram', 'as-built diagram', 'runtime flow…

jonathan-vella/apex-accelerator · 99 tokens

aws-architecture-diagram

Generate AWS architecture diagrams in draw.io format. Activates when the user asks to create, generate, or build an architecture diagram, system diagram, or draw.io diagram for AWS services.

vidanov/aws-architecture-diagram-skill · 43 tokens