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 kirogit 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/kiro)<a href="https://agentmods.dev/skills/vidanov/aws-architecture-diagram-skill/kiro"><img src="https://agentmods.dev/badge/skills/vidanov/aws-architecture-diagram-skill/kiro/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/kiro"><img src="https://agentmods.dev/badge/skills/vidanov/aws-architecture-diagram-skill/kiro.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.00043 | $0.05281 |
| Opus 5 | $0.00022 | $0.02641 |
| Sonnet 5 | $0.00009 | $0.01056 |
| Haiku 4.5 | $0.00004 | $0.00528 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions
Generate a draw.io (.drawio) XML file representing an AWS architecture diagram.
Layout
- 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 (to leave room for edge labels)
- Minimum 250px vertical spacing between lanes (so vertical edges don't crowd)
- Secondary/auxiliary services (monitoring, DLQ, error paths) go BELOW the main flow with 280px+ vertical gap
Canvas
- Large canvas:
pageWidth="2400" pageHeight="1400"minimum - Set
dx="2800" dy="1600"for proper viewport - Always include a title block as the first element after the background:
<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/, updated quarterly) - Icon size: 78x78px for main services, 65x65px for secondary
- Use
sketch=0;outlineConnect=0;on all icons - Use
strokeColor=#ffffffon all AWS service icons - MUST include
fillColor— without it, icons render as invisible/white in PNG export - Font size: 12px for labels
- Always include:
fontColor=#232F3E;verticalLabelPosition=bottom;verticalAlign=top;align=center;html=1;aspect=fixed;
fillColor by AWS service category:
| Category | fillColor | Services |
|---|---|---|
| Compute | #ED7100 |
Lambda, EC2, ECS, EKS, Fargate |
| Networking | #8C4FFF |
VPC, ELB, CloudFront, Route 53, API Gateway |
| Database | #C925D1 |
RDS, DynamoDB, Aurora, ElastiCache |
| Storage | #3F8624 |
S3, EFS, EBS |
| Security | #DD344C |
IAM, Cognito, KMS, WAF |
| Integration | #E7157B |
SQS, SNS, EventBridge, Step Functions |
| Analytics | #8C4FFF |
Kinesis, Athena, Redshift |
| Management | #E7157B |
CloudWatch, CloudTrail |
| AI/ML | #01A88D |
Bedrock, SageMaker |
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.
- 11d ago First seen · 288 lines · 43 tokens per session scan A 0119ad21aa63
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 43 tokens to every session and 5,281 once invoked, about $0.0002 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
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"…
oci-drawio-icon-native
Build and validate OCI draw.io diagrams in icon-native mode so they never depend on mxgraph.oci. runtime libraries. Use when authoring or fixing Oracle Cloud architecture diagrams in draw.io that must render portably.
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…
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
AWS architecture diagrams — generate visual network topology diagrams from live AWS infrastructure. Use when drawing AWS network diagrams, visualizing VPCs, mapping Transit Gateway topology, or generating architecture documentation.