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 agentmods add skills/eliecer2000/kiro-bootstrap/aws-lambda-pythonnpx skills add eliecer2000/kiro-bootstrap --skill aws-lambda-pythongit clone --depth 1 https://github.com/eliecer2000/kiro-bootstrapWhat 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 | $0.00036 | $0.02241 |
| Opus 5 | $0.00018 | $0.01120 |
| Sonnet 5 | $0.00007 | $0.00448 |
| Haiku 4.5 | $0.00004 | $0.00224 |
Grade A, and why
aws-lambda-python 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 yesterday.
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 — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Lambda Python
Skill para desarrollo de funciones Lambda en Python: handlers, empaquetado, layers, AWS SDK (boto3), Powertools, logging estructurado, manejo de errores, testing y mejores prácticas de rendimiento.
Principios fundamentales
- Un handler, una responsabilidad. Evitar Lambdas monolíticos.
- Separar lógica de negocio del handler. El handler solo parsea el evento, invoca la lógica y formatea la respuesta.
- Usar AWS Lambda Powertools para Python en todo proyecto: logging, tracing, metrics, validation, idempotency.
- Tipado estricto con type hints y validación con Pydantic o Powertools Parser.
- Inicializar clientes AWS fuera del handler (reutilización en warm starts).
Estructura de proyecto recomendada
functions/
├── mi_funcion/
│ ├── __init__.py
│ ├── handler.py # Entry point del Lambda
│ ├── service.py # Lógica de negocio
│ ├── repository.py # Acceso a datos (DynamoDB, S3, etc.)
│ ├── models.py # Pydantic models / dataclasses
│ └── exceptions.py # Excepciones custom
├── shared/
│ ├── __init__.py
│ ├── middleware.py # Middleware compartido
│ └── constants.py
├── tests/
│ ├── unit/
│ │ ├── test_service.py
│ │ └── test_handler.py
│ └── integration/
│ └── test_api.py
├── requirements.txt
└── pyproject.toml
Handler con Powertools (patrón recomendado)
from aws_lambda_powertools import Logger, Tracer, Metrics
from aws_lambda_powertools.event_handler import APIGatewayHttpResolver
from aws_lambda_powertools.logging import correlation_paths
from aws_lambda_powertools.metrics import MetricUnit
from aws_lambda_powertools.utilities.typing import LambdaContext
from aws_lambda_powertools.utilities.validation import validate
logger = Logger()
tracer = Tracer()
metrics = Metrics()
app = APIGatewayHttpResolver()
# Clientes AWS inicializados fuera del handler (warm start reuse)
import boto3
dynamodb = boto3.resource("dynamodb")
table = dynamodb.Table(os.environ["TABLE_NAME"])
@app.get("/items")
@tracer.capture_method
def list_items():
items = table.query(
KeyConditionExpression="PK = :pk",
ExpressionAttributeValues={":pk": "ITEMS"},
)
return {"items": items.get("Items", [])}
@app.post("/items")
@tracer.capture_method
def create_item():
body = app.current_event.json_body
# Validar con Pydantic
item = ItemCreate(**body)
table.put_item(Item=item.to_dynamo())
metrics.add_metric(name="ItemCreated", unit=MetricUnit.Count, value=1)
return {"id": item.id}, 201
@logger.inject_lambda_context(correlation_id_path=correlation_paths.API_GATEWAY_HTTP)
@tracer.capture_lambda_handler
@metrics.log_metrics(capture_cold_start_metric=True)
def handler(event: dict, context: LambdaContext) -> dict:
return app.resolve(event, context)
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.
- yesterday First seen · 286 lines · 36 tokens per session scan A 65dcb4c22901
aws-lambda-python is a skill published in the GitHub repository eliecer2000/kiro-bootstrap (9 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 2,241 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
cognito-passkey-auth
Amazon Cognito — Custom UI with Passkeys, Social Login & Face ID. Reference skill (loaded via skill:// from the ios agent).
amazon-location-service
Amazon Location Service. Reference skill (loaded via skill:// from the ios agent).
amazon-polly-generative
Amazon Polly Generative Voices. Reference skill (loaded via skill:// from the ios agent).
amazon-bedrock
Builds generative AI applications on Amazon Bedrock. Covers model invocation (Converse API, InvokeModel), RAG with Knowledge Bases, Bedrock Agents, Guardrails, and AgentCore. Use when invoking models, setting up Knowledge Bases, creating agents, applying guardrails, deploying to AgentCore, troubleshooting Bedrock…
verify-pr
Comprehensive PR readiness check before merge. Run quality checks, tests, CI, documentation, AWS resource cleanup, and code review.
run-integ
Run integration tests (deploy + destroy) against real AWS. Use when you need to verify cdkd works end-to-end with actual AWS resources.