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 vidanov/aws-architecture-diagram-skill --skill claudegit clone --depth 1 https://github.com/vidanov/aws-architecture-diagram-skillWrote 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/vidanov/aws-architecture-diagram-skill/claude)<a href="https://agentmods.dev/skills/vidanov/aws-architecture-diagram-skill/claude"><img src="https://agentmods.dev/badge/skills/vidanov/aws-architecture-diagram-skill/claude/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/vidanov/aws-architecture-diagram-skill/claude"><img src="https://agentmods.dev/badge/skills/vidanov/aws-architecture-diagram-skill/claude.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00057 | $0.04838 |
| Opus 5 | $0.00028 | $0.02419 |
| Sonnet 5 | $0.00011 | $0.00968 |
| Haiku 4.5 | $0.00006 | $0.00484 |
Grade A, and why
aws-architecture-diagram 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 12d 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 — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Architecture Diagram Skill
Generate AWS architecture diagrams as native .drawio files using official AWS Architecture Icons. Optionally export to PNG, SVG, or PDF with embedded XML (so exported files remain editable in draw.io).
How to create a diagram
- Generate draw.io XML in mxGraphModel format following the rules below
- Write the XML to a
.drawiofile using the Write tool - If the user requested an export format (png, svg, pdf), export using the draw.io CLI (see Export section)
- Open the result with
open(macOS),xdg-open(Linux), or print the path
Layout Rules
- Left-to-right flow for data/request path
- UI/Frontend on the LEFT (users access from left side)
- Data sources / external systems on the RIGHT
- Use horizontal lanes for parallel paths (top lane, bottom lane)
- Minimum 220px horizontal spacing between icons (room for edge labels)
- Minimum 250px vertical spacing between lanes
- Secondary/auxiliary services (monitoring, DLQ) go BELOW main flow with 280px+ gap
- Canvas:
pageWidth="2400" pageHeight="1400", viewportdx="2800" dy="1600" - Always include a title block after the background rectangle:
<mxCell value="<b>Diagram Title</b><br>Author | Date | Version" style="text;html=1;align=left;verticalAlign=top;whiteSpace=wrap;rounded=0;fontSize=14;spacing=8;" vertex="1" parent="1">
<mxGeometry x="40" y="30" width="420" height="60" as="geometry" />
</mxCell>
Icon Style
- Icons are from draw.io's built-in
mxgraph.aws4stencil library — the official AWS Architecture Icons (https://aws.amazon.com/architecture/icons/) - Icon size: 78x78px for main services, 65x65px for secondary
- Use
sketch=0on all icons - Use
strokeColor=#ffffffon all AWS service icons - Font size: 12px for labels
- NO colored backgrounds on group boxes — always
fillColor=none
3D / Isometric Diagrams — use a different icon library
If the user asks for a 3D, isometric, or "AWS 3D" diagram, do NOT fake it by placing flat aws4 icons on hand-built platform/pedestal shapes. draw.io has a real, separate built-in library for this: mxgraph.aws3d.*.
- Load
references/aws-icons-3d.mdbefore picking any icon — it has the verified shape table, style prefix, sizes, and the nativeisometricEdgeStyleedge templates. - This library is a legacy pre-2019 icon set with much smaller coverage than
aws4(no API Gateway, ECS/EKS/Fargate, Step Functions, EventBridge, SNS, Aurora, CloudWatch, IAM, etc.). Check the gap table in that reference file before assuming an icon exists, and flag substitutions to the user rather than guessing a stencil name. - For generic hardware (clients, on-prem servers, racks, switches) with no AWS-specific icon, see
references/aws-icons-allied-telesis.md— a separate bundled isometric image library that fills that gap. - These icons are already 3D on their own — arrange them in an ascending isometric staircase (diagonal offsets between nodes), don't add fake platforms underneath.
- Use
edgeStyle=isometricEdgeStyle(withendArrow=blockoverride for reliable arrowheads) instead oforthogonalEdgeStylefor connectors.
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.
- 12d ago First seen · 299 lines · 57 tokens per session scan A c0a67d34ca10
aws-architecture-diagram is a skill published in the GitHub repository vidanov/aws-architecture-diagram-skill (148 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 4,838 once invoked, about $0.0003 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-30.
Other skills, from other repositories
auditing-aws-s3-bucket-permissions
Systematically audit AWS S3 bucket permissions to identify publicly accessible buckets, overly permissive ACLs, misconfigured bucket policies, and missing encryption settings using AWS CLI, S3audit, and Prowler to enforce least-privilege data access controls.
detecting-aws-cloudtrail-anomalies
Detect unusual API call patterns in AWS CloudTrail logs using boto3, statistical baselining, and behavioral analysis to identify credential compromise, privilege escalation, and unauthorized resource access.
serverless-architecture
Designs and implements serverless functions: function boundary design, runtime selection, event sources, IAM least privilege, configuration, observability, and cost estimation. Invoked when the user asks to build a serverless function, design a Lambda-based system, or move workloads to serverless.
create-terraform-module
Creates or updates AWS-oriented Terraform module structure and implementation scaffolding. Focuses on file layout, variable/output contracts, provider and version constraints, tagging standards, safe composition patterns, and address-stability guardrails.
design-aws-terraform-iac
Designs AWS-targeted Terraform infrastructure plans before implementation. Focuses on service selection, module boundaries, state/backends, environment separation, security/compliance guardrails, acceptance criteria, and explicit risk/validation assumptions.
drawio-aws-reference
Produce AWS architecture diagrams as editable .drawio files using the AWS 2026 shape set (mxgraph.aws4 stencils), with verified stencil names and a validator. Use this whenever an AWS architecture diagram is requested, revised, or reviewed, including when the user only says "draw the architecture", "diagram this"…