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 patvillarroel/drawio-aws-reference --skill drawio-aws-referencegit clone --depth 1 https://github.com/patvillarroel/drawio-aws-referenceWrote 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/patvillarroel/drawio-aws-reference/drawio-aws-reference)<a href="https://agentmods.dev/skills/patvillarroel/drawio-aws-reference/drawio-aws-reference"><img src="https://agentmods.dev/badge/skills/patvillarroel/drawio-aws-reference/drawio-aws-reference/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/patvillarroel/drawio-aws-reference/drawio-aws-reference"><img src="https://agentmods.dev/badge/skills/patvillarroel/drawio-aws-reference/drawio-aws-reference.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.00119 | $0.04043 |
| Opus 5 | $0.00060 | $0.02021 |
| Sonnet 5 | $0.00024 | $0.00809 |
| Haiku 4.5 | $0.00012 | $0.00404 |
Grade A, and why
drawio-aws-reference 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 9d 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 — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS architecture diagrams in draw.io
The goal is to hand over a .drawio file the user can open and adjust without
rebuilding nodes. Most rework comes from four mechanical mistakes, and all four
are avoidable by following this spec literally.
Mermaid is fine for iterating on the logic inside the conversation. The
deliverable is always .drawio.
Source of truth
When the user supplies both a prose description and a Mermaid sketch, the prose wins. Mermaid is a convenience for reading the shape of the system, and it drops detail: a flow mentioned in the description but missing from the diagram is still a flow.
Read both, then check for orphans: any resource with no edge in or out. A bucket nothing writes to, a queue nothing reads, a database nobody queries. An orphan is almost always a gap in the source description rather than a real dead end. Ask before drawing it, and say which flow you think is missing.
Required workflow
- Settle the logic of the diagram in text or Mermaid, and confirm it with the user before writing any XML.
- Look up every name: service icons in
reference/resicons.txt, VPC sub-components and actors inreference/shapes.txt, containers inreference/groups.md. Never write a stencil name from memory. - Write the
.drawiofile. - Run
scripts/validate.pyagainst it and fix everything it reports as an error. - Deliver, and close with the handover note below.
Step 4 is not optional. A diagram that has not passed the validator is not delivered.
Handover note
The validator checks the mechanics. It cannot see the rendered result, so spacing that is technically legal can still look wrong, and an edge label can still land somewhere awkward. Say so when handing the file over, in the user's language, in one or two sentences. Something along these lines:
El diagrama puede necesitar retoques menores. Puedes resolverlos en draw.io, o exportarme el PNG en modo claro y sin fondo transparente y lo ajusto yo.
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.
- 9d ago First seen · 348 lines · 119 tokens per session scan A 23b9ebaac45f
drawio-aws-reference is a skill published in the GitHub repository patvillarroel/drawio-aws-reference (8 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 119 tokens to every session and 4,043 once invoked, about $0.0006 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 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…
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.
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…
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…
drawio-skill
Create, edit, synchronize, inspect, test, and publish editable draw.io diagrams. Use when the user explicitly requests draw.io/diagrams.net, needs a polished architecture, ERD, UML, sequence, C4, SysML, BPMN, network, swimlane, ML, or infrastructure diagram, wants code/IaC/SQL/OpenAPI converted into a diagram, or…
aws-architecture-diagram
Generate validated AWS architecture diagrams as draw.io XML using official AWS4 icon libraries. Use this skill whenever the user wants to create, generate, or design AWS architecture diagrams, cloud infrastructure diagrams, or system design visuals. Also triggers for requests to visualize existing infrastructure from…