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 seandkendall/kiro-config --skill aws-architecture-diagramgit clone --depth 1 https://github.com/seandkendall/kiro-configWrote 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/seandkendall/kiro-config/aws-architecture-diagram)<a href="https://agentmods.dev/skills/seandkendall/kiro-config/aws-architecture-diagram"><img src="https://agentmods.dev/badge/skills/seandkendall/kiro-config/aws-architecture-diagram/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/seandkendall/kiro-config/aws-architecture-diagram"><img src="https://agentmods.dev/badge/skills/seandkendall/kiro-config/aws-architecture-diagram.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.00055 | $0.01199 |
| Opus 5.5 | $0.00022 | $0.00480 |
| Sonnet 5.5 | $0.00011 | $0.00240 |
| Haiku 4.5 | $0.00006 | $0.00120 |
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 today.
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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Architecture Diagram Generator
Generate draw.io XML files with official AWS4 icons matching the style of AWS Reference Architecture diagrams.
When to Use This Skill vs. aws-diagram-png
- Use this skill (
aws-architecture-diagram) when the user wants editable draw.io XML they can refine in app.diagrams.net before exporting - Use
aws-diagram-png(the awsdac-based skill) when the user wants a PNG image directly for slides, docs, or PRs - Use
aws-diagram-htmlwhen the user wants a polished, self-contained HTML page (inline SVG, official icons, verified non-overlapping lines) to open in a browser
The two skills use different AWS icon libraries:
| Skill | Icon namespace | Output |
|---|---|---|
aws-architecture-diagram (this) |
mxgraph.aws4.* (draw.io's bundled AWS4 set) |
.drawio XML |
aws-diagram-png |
awsdac's definition-for-aws-icons-light.yaml |
.png image |
Resource type names differ between the two — this skill uses draw.io's resIcon=mxgraph.aws4.<service>, while aws-diagram-png uses CloudFormation-style AWS::<Service>::<Resource> with awsdac-specific fallback rules. Don't mix the two.
Modes
Mode A — Codebase Analysis
If user says "analyze", "scan", "from code", or references their existing project:
- Scan for infrastructure files: CloudFormation, CDK (
cdk.json), Terraform (resource "aws_*") - Extract services, relationships, VPC structure, and data flow
- For non-AWS technologies (Docker, databases, ML frameworks), map to general icons
- Confirm discovered architecture with user before generating
Mode B — Brainstorming
If user describes an architecture or says "brainstorm"/"design"/"from scratch":
- Ask 3-5 focused questions (purpose, services, scale, security, traffic pattern)
- Propose the architecture with service recommendations and data flow
- Iterate if needed, then generate
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.
- today First seen · 99 lines · 55 tokens per session scan A 468047c2f124
aws-architecture-diagram is a skill published in the GitHub repository seandkendall/kiro-config (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 55 tokens to every session and 1,199 once invoked, about $0.0002 per session on Opus 5.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-10-27.
Other skills, from other repositories
aws-cdk
AWS CDK infrastructure development in TypeScript. Use when creating stacks, constructs, L2/L3 patterns, CDK testing, synth/deploy pipelines or organizing IaC code.
aws-serverless
Building production-ready serverless applications on AWS. Use when working with Lambda, API Gateway, SQS, SNS, DynamoDB Streams, SAM/CDK deployment or optimizing cold starts.
aws-terraform
AWS infrastructure with Terraform. Use when creating modules, managing remote state, writing tftest.hcl tests, refactoring IaC or following HashiCorp style guide.
aws-architecture
AWS architecture decisions, serverless patterns, event-driven design, service boundaries and Well-Architected Framework. Use when designing system architecture or making infrastructure tradeoffs.
aws-lambda-python
AWS Lambda development with Python. Use when writing Lambda handlers, packaging with layers, using boto3/Powertools, structured logging or optimizing Python Lambda performance.
aws-api
AWS API design, implementation and integration patterns. Use when creating or modifying API Gateway endpoints, OpenAPI contracts, authentication, error handling or event integrations.