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 deploy-on-awsgit 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/deploy-on-aws)<a href="https://agentmods.dev/skills/seandkendall/kiro-config/deploy-on-aws"><img src="https://agentmods.dev/badge/skills/seandkendall/kiro-config/deploy-on-aws/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/deploy-on-aws"><img src="https://agentmods.dev/badge/skills/seandkendall/kiro-config/deploy-on-aws.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.00065 | $0.01529 |
| Opus 5.5 | $0.00026 | $0.00612 |
| Sonnet 5.5 | $0.00013 | $0.00306 |
| Haiku 4.5 | $0.00006 | $0.00153 |
Grade A, and why
deploy-on-aws 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy on AWS
Take any application and deploy it to AWS with minimal user decisions.
Philosophy
Minimize cognitive burden. User has code, wants it on AWS. Pick the most straightforward services. Don't ask questions with obvious answers.
Workflow
- Analyze - Scan codebase for framework, database, dependencies
- Recommend - Select AWS services, concisely explain rationale
- Estimate - Show monthly cost before proceeding
- Generate - Write IaC code with security defaults applied
- Quality Gate - Run the Pre-Deployment Quality Gate from
development-workflow.md: lint (zero warnings), build (zero warnings), unit tests (≥90% coverage), Playwright E2E (target 100%), no deprecation notices, no critical/high vulnerabilities - Deploy - Run security checks (cdk-nag), then execute via
deploy.sh
Defaults
Default to dev-sized (cost-conscious: small instance sizes, minimal redundancy, single-AZ) unless user says "production-ready".
MCP Server Usage (AWS Agent Toolkit)
Use the unified AWS MCP Server (aws-mcp-server, via mcp-proxy-for-aws) for all AWS interactions. Resolve the actual callable tool name via tool_search before invoking any of these — see steering/aws-agent-toolkit.md → "Resolving the correct tool name" if a call fails with "Tool is not available":
- Architecture decisions: the AWS docs-search tool (
search_documentation, filter byagent_skills) and the skill-retrieval tool (retrieve_skill) to load curated guidance before designing - API knowledge: the AWS docs-search tool (topic
current_awarenessorreference_documentation) to verify the exact API/CLI syntax — never guess. There is no dedicated "suggest commands" tool; docs search is the current path for this. - Cost estimates: the sandboxed-Python tool (
run_script) to invoke the Pricing API or Cost Explorer directly — this is the only AWS-API-call tool now (call_awswas removed Aug 31, 2026). Always present costs before generating IaC so the user can adjust before committing - IaC validation: the sandboxed-Python tool (
run_script) for sandboxed Python checks (e.g., synth a CDK stack and inspect the template)
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 114 lines · 65 tokens per session scan A eb26a8be2c85
deploy-on-aws is a skill published in the GitHub repository seandkendall/kiro-config (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 65 tokens to every session and 1,529 once invoked, about $0.0003 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.