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 hoangatg/ai-agent-toolkit --skill aws-serverlessgit clone --depth 1 https://github.com/hoangatg/ai-agent-toolkitWrote 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/hoangatg/ai-agent-toolkit/aws-serverless)<a href="https://agentmods.dev/skills/hoangatg/ai-agent-toolkit/aws-serverless"><img src="https://agentmods.dev/badge/skills/hoangatg/ai-agent-toolkit/aws-serverless/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/hoangatg/ai-agent-toolkit/aws-serverless"><img src="https://agentmods.dev/badge/skills/hoangatg/ai-agent-toolkit/aws-serverless.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.00035 | $0.01028 |
| Opus 5.5 | $0.00014 | $0.00411 |
| Sonnet 5.5 | $0.00007 | $0.00206 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
aws-serverless 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 1mo 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Serverless
Pay for what you use. Scale to zero. Ship faster.
1. Serverless Architecture
Core Services
| Service | Purpose | Use When |
|---|---|---|
| Lambda | Compute | Event-driven functions |
| API Gateway | HTTP endpoints | REST/WebSocket APIs |
| DynamoDB | Database | Key-value, high throughput |
| S3 | Storage | Files, static assets |
| SQS | Queue | Async processing |
| SNS | Pub/Sub | Fan-out notifications |
| EventBridge | Event bus | Cross-service events |
| Step Functions | Orchestration | Complex workflows |
2. Lambda Design Principles
Function Design
| Principle | Application |
|---|---|
| Single responsibility | One function, one purpose |
| Stateless | No local state between invocations |
| Idempotent | Safe to retry |
| Fast startup | Minimize cold start impact |
| Small package | Only include what's needed |
Cold Start Optimization
| Strategy | Impact |
|---|---|
| Smaller runtime (Node.js, Python) | Lower cold start |
| Minimize dependencies | Faster init |
| Provisioned concurrency | Eliminate cold starts |
| SnapStart (Java) | 10x faster Java cold starts |
| ARM (Graviton2) | 20% cheaper, similar performance |
Memory & Timeout
Memory Decision:
├── CPU-bound → More memory = more CPU = faster
├── IO-bound → Minimum memory needed
└── Sweet spot: Profile and benchmark
Timeout Decision:
├── API response → 3-10 seconds max
├── Background processing → up to 15 minutes
└── Always set explicit timeout (never default)
3. API Gateway Patterns
API Design
| Pattern | Use Case |
|---|---|
| REST API | Standard CRUD, caching |
| HTTP API | Simple proxy, lower cost |
| WebSocket | Real-time, chat, notifications |
Best Practices
- Use request validation (models/schemas)
- Enable throttling and usage plans
- Implement API keys for external clients
- Use stages for dev/staging/prod
- Enable access logging
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.
- 1mo ago First seen · 159 lines · 35 tokens per session scan A 3098114fbda7
aws-serverless is a skill published in the GitHub repository hoangatg/ai-agent-toolkit (1 stars, last pushed 7mo ago), licensed MIT. It adds 35 tokens to every session and 1,028 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
springboot-patterns
Spring Boot architecture patterns, REST API design, layered services, data access, caching, async processing, and logging. Use for Java Spring Boot backend work.
django-patterns
Django architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware, and production-grade Django apps.
api-design
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
azure-functions
Build, review, or migrate Azure Functions in .NET with correct execution model, isolated worker setup, bindings, DI, and Durable Functions patterns. USE FOR: working on Azure Functions in .NET; migrating from the in-process model to the isolated worker model; adding Durable Functions, bindings, or host configuration.…
gcp-essentials
Use when running a small product on core Google Cloud via the gcloud CLI: a project, Cloud Run deploys, a locked-down Cloud Storage bucket, managed Cloud SQL, and least-privilege IAM wiring them together. NOT AWS (that is aws-essentials), NOT the CI pipeline that ships the image (that is deployment), NOT Postgres…