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-diagram-pnggit 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-diagram-png)<a href="https://agentmods.dev/skills/seandkendall/kiro-config/aws-diagram-png"><img src="https://agentmods.dev/badge/skills/seandkendall/kiro-config/aws-diagram-png/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-diagram-png"><img src="https://agentmods.dev/badge/skills/seandkendall/kiro-config/aws-diagram-png.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.00061 | $0.01989 |
| Opus 5.5 | $0.00024 | $0.00796 |
| Sonnet 5.5 | $0.00012 | $0.00398 |
| Haiku 4.5 | $0.00006 | $0.00199 |
Grade A, and why
aws-diagram-png 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Diagram PNG Generator (awsdac)
Generate production-ready PNG diagrams with official AWS architecture icons using the awsdac CLI tool. Use this skill when the user wants a PNG image (not draw.io XML).
When to Use This Skill vs. aws-architecture-diagram
- Use this skill (
aws-diagram-png) when the user wants a PNG file directly, a ready-to-share image, or a diagram for a slide/doc - Use
aws-architecture-diagramwhen the user wants editable draw.io XML that they can modify later in app.diagrams.net - Use
aws-diagram-htmlwhen the user wants a polished HTML page with hand-routed connectors that never overlap (awsdac auto-layout can route lines across each other)
Prerequisites
awsdac must be installed on the user's machine:
# macOS
brew install awsdac
# Go 1.21+
go install github.com/awslabs/diagram-as-code/cmd/awsdac@latest
Verify with: awsdac --version
Workflow
Mode A — Codebase Analysis
If the user says "analyze", "scan", "from code", or references their existing project:
- Scan for infrastructure files: CloudFormation (
*.yaml,*.json), CDK (cdk.json,app.py), Terraform (*.tf) - Extract services, relationships, VPC structure, and data flow
- Confirm discovered architecture with the user before generating
- Shortcut: If the user has a CloudFormation template, use
awsdac -c template.yamlto auto-generate the diagram directly (beta feature)
Mode B — Brainstorming / From Scratch
If the 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
Generation Steps
- Write the YAML file (see structure below) to a sensible path — typically
docs/diagrams/<name>.yamlorarchitecture/<name>.yaml - Run:
awsdac <name>.yaml -o <name>.png - Verify the PNG was created: check that output file exists and is non-zero size
- Tell the user the path to the generated PNG
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 · 204 lines · 61 tokens per session scan A adf8c63a6a84
aws-diagram-png is a skill published in the GitHub repository seandkendall/kiro-config (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 61 tokens to every session and 1,989 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.