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 agentmods add instructions/clouddaddyza/visiointegration/copilot-instructionsgit clone --depth 1 https://github.com/CloudDaddyZA/VisioIntegrationWrote 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/instructions/clouddaddyza/visiointegration/copilot-instructions)<a href="https://agentmods.dev/instructions/clouddaddyza/visiointegration/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/clouddaddyza/visiointegration/copilot-instructions.svg" alt="Measured on agentmods" 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 | $0.01690 | $0.01690 |
| Opus 5 | $0.00845 | $0.00845 |
| Sonnet 5 | $0.00338 | $0.00338 |
| Haiku 4.5 | $0.00169 | $0.00169 |
Grade A, and why
VisioIntegration copilot-instructions.md 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 3d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions — Azure Visio MCP
Project Overview
This is an MCP (Model Context Protocol) server for creating production-quality Azure architecture diagrams. It exposes 31 tools, 8 resources, and 7 prompts via FastMCP (Python) and is consumed by:
- A Streamlit web app (
app/) - A VS Code extension with GitHub Copilot Chat participant
@azureVisio(vscode-extension/) - A PyInstaller desktop app (
desktop.spec)
Architecture
- MCP Server:
src/visio_mcp/server.py— central tool hub - Data Models:
src/visio_mcp/models.py— Pydantic models (DiagramState, DiagramResource, Connection, BoundaryGroup) - State Manager:
src/visio_mcp/diagram_state.py— DiagramManager class - Renderers:
visio_engine.py(.vsdx via COM),drawio_engine.py(.drawio XML), andmermaid_engine.py(.mmd flowchart text) - Validators:
waf_validator.py(5 WAF pillars) andcaf_validator.py(7 CAF principles) - Layout:
layout_engine.py— tiered/grid/grouped auto-layout - Catalog:
azure_catalog.py— 151 Azure resource shapes with SVG icon paths - References:
reference_architectures.py— 16 templates, 14 styles, 50 design patterns - Pricing:
azure_sku_grounding.py— live Azure Retail Prices API
Key Conventions
Resource Types
Always use the canonical resource_type from AZURE_SHAPE_CATALOG (e.g., virtual_machine, app_service, sql_database). Common aliases are resolved automatically (aks → kubernetes_service, apim → api_management, vm → virtual_machine).
CAF Naming
Resources should follow Cloud Adoption Framework naming prefixes:
- VMs:
vm-, App Services:app-, SQL:sql-, VNets:vnet-, Subnets:snet- - Key Vault:
kv-, Storage:st, AKS:aks-, Container Registry:cr
Boundary Types
Use: resource_group, virtual_network, subnet, subscription, region, availability_zone, security_boundary
Positions & Layout
- Coordinates are in inches (Visio page units). Default page: 11×8.5 inches.
- Let
auto_layouthandle positioning — don't hardcode unless replicating a reference architecture. - When adding resources to a boundary with
group_id, positions auto-calculate.
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.
- 3d ago First seen · 147 lines · 1,690 tokens per session scan A b829d5155829
VisioIntegration copilot-instructions.md is an instructions file published in the GitHub repository CloudDaddyZA/VisioIntegration (2 stars, last pushed 2mo ago), licensed MIT. It adds 1,690 tokens to every session, about $0.0085 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.
Other instructions, from other repositories
azure-search-openai-demo bicep.instructions.md
Infrastructure as Code with Bicep.
azure-sdk-for-rust resourcemanager.instructions.md
Instructions for Azure/azure-sdk-for-rust, a project described as: This repository is for the active development of the Azure SDK for Rust. For consumers of the SDK we recommend visiting Docs.rs and looking up the docs for any of libraries in the SDK.
azure-sdk-for-rust AGENTS.md
Instructions for Azure/azure-sdk-for-rust, covering agents.md, repository overview, repository structure, agent capabilities and recommended actions.
azure-dev extensions.instructions.md
Instructions for Azure/azure-dev, a project described as: A developer CLI for working with Azure resources to build and deploy AI applications. Commands map to key workflow stages: code, build, deploy, and monitor.
azure-dev AGENTS.md
Instructions for Azure/azure-dev, a project described as: A developer CLI for working with Azure resources to build and deploy AI applications. Commands map to key workflow stages: code, build, deploy, and monitor.
drawio-ai-kit AGENTS.md
Instructions for sparklabx/drawio-ai-kit, covering repository guidelines, tech stack & runtime and code conventions & common patterns.