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 eliecer2000/kiro-bootstrap --skill aws-cdkgit clone --depth 1 https://github.com/eliecer2000/kiro-bootstrapWrote 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/eliecer2000/kiro-bootstrap/aws-cdk)<a href="https://agentmods.dev/skills/eliecer2000/kiro-bootstrap/aws-cdk"><img src="https://agentmods.dev/badge/skills/eliecer2000/kiro-bootstrap/aws-cdk.svg" alt="Measured on agentmods" 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.00040 | $0.02830 |
| Opus 5 | $0.00020 | $0.01415 |
| Sonnet 5 | $0.00008 | $0.00566 |
| Haiku 4.5 | $0.00004 | $0.00283 |
Grade A, and why
aws-cdk 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 8d 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 — 373 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS CDK
Skill para desarrollo de infraestructura con AWS CDK en TypeScript: stacks, constructs, patrones L2/L3, testing, synth, deploy, pipelines CI/CD y mejores prácticas de organización de código IaC.
Principios fundamentales
- CDK es código, trátalo como tal: tests, code review, linting, CI/CD.
- Preferir constructs L2 (aws-xxx) sobre L1 (CfnXxx). L1 solo cuando L2 no expone la propiedad necesaria.
- Un stack = una unidad de deployment. No meter toda la infra en un solo stack.
- Nombres lógicos estables: evitar cambios que fuercen replacement de recursos stateful.
- Nunca hardcodear account IDs, regiones o ARNs. Usar
Aws.ACCOUNT_ID,Aws.REGION, SSM lookups o context.
Estructura de proyecto recomendada
infra/
├── bin/
│ └── app.ts # Entry point, instancia stacks
├── lib/
│ ├── stacks/
│ │ ├── api-stack.ts # Stack de API Gateway + Lambda
│ │ ├── data-stack.ts # Stack de DynamoDB, S3
│ │ └── auth-stack.ts # Stack de Cognito
│ ├── constructs/
│ │ ├── api-lambda.ts # Construct reutilizable
│ │ └── monitored-table.ts
│ └── config/
│ └── environments.ts # Configuración por ambiente
├── test/
│ ├── stacks/
│ │ └── api-stack.test.ts
│ └── constructs/
│ └── api-lambda.test.ts
├── cdk.json
├── tsconfig.json
└── package.json
Configuración por ambiente
interface EnvironmentConfig {
readonly account: string;
readonly region: string;
readonly stageName: string;
readonly domainName?: string;
readonly logRetentionDays: number;
readonly removalPolicy: cdk.RemovalPolicy;
}
const environments: Record<string, EnvironmentConfig> = {
dev: {
account: process.env.CDK_DEFAULT_ACCOUNT!,
region: 'us-east-1',
stageName: 'dev',
logRetentionDays: 7,
removalPolicy: cdk.RemovalPolicy.DESTROY,
},
prod: {
account: '123456789012',
region: 'us-east-1',
stageName: 'prod',
logRetentionDays: 365,
removalPolicy: cdk.RemovalPolicy.RETAIN,
},
};
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.
- 8d ago First seen · 373 lines · 40 tokens per session scan A f44bbd5f55cf
aws-cdk is a skill published in the GitHub repository eliecer2000/kiro-bootstrap (9 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 2,830 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-31.
Other skills, from other repositories
deno-knowledge-patch
Use this skill when choosing current Deno runtime APIs, CLI options, configuration, dependency behavior, Node compatibility, or deployment workflows. Open the topic reference before changing a project because several commands, flags, APIs, and defaults changed more than once.
sandy
Run TypeScript scripts in sandboxed microVMs or Docker containers with AWS SDK access via IMDS. Use when investigating AWS resources, running read-only queries, or executing TypeScript automation that needs AWS credentials.
aws-cdk-builder
AWS CDK infrastructure builder using TypeScript with L2/L3 constructs and Well-Architected patterns. Activate on: AWS CDK, CDK construct, CDK stack, CDK pipeline, AWS infrastructure as code TypeScript, L2 construct, CDK patterns. NOT for: Terraform IaC (use terraform-module-builder), Kubernetes manifests (use…
aws-sst-development
SST v4 (Ion) expert for managing AWS resources as code with the Pulumi-backed framework.
agent-squad-typescript
Use when building or modifying a Node.js / TypeScript app that uses the agent-squad npm package — multi-agent orchestration: orchestrator, agents (all built-in types + GroundedAgent), classifier routing (Bedrock / Anthropic / OpenAI), storage (in-memory / DynamoDB / SQL), retrievers (Amazon KB / Dakera), and tools…
node-modules-inspector
Inspects a project's installed nodemodules and produces three reports: duplicated packages (installed in multiple versions), packages sorted by install size, and maintenance actions (dep-upgrade opportunities + publint findings, grouped by consumer/author). Use when the user wants to audit dependencies, find duplicate…