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 soulcodex/agentic --skill serverless-architecturegit clone --depth 1 https://github.com/soulcodex/agenticWrote 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/soulcodex/agentic/serverless-architecture)<a href="https://agentmods.dev/skills/soulcodex/agentic/serverless-architecture"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/serverless-architecture/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/soulcodex/agentic/serverless-architecture"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/serverless-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00062 | $0.01177 |
| Opus 5.5 | $0.00025 | $0.00471 |
| Sonnet 5.5 | $0.00012 | $0.00235 |
| Haiku 4.5 | $0.00006 | $0.00118 |
Grade A, and why
serverless-architecture 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Serverless Architecture Skill
Step 1 — Function Boundary Design
A Lambda function (or equivalent) should do exactly one thing. Design boundaries by:
- Event source: each distinct trigger gets its own function.
- Single responsibility: one function = one business operation.
- Avoid chaining: do not call one Lambda synchronously from another — use queues.
Bad: process-order Lambda → calls fulfillment Lambda → calls notification Lambda
Good: process-order Lambda → SQS → fulfillment Lambda → SQS → notification Lambda
Step 2 — Runtime and Cold-Start
| Runtime | Cold-start | Notes |
|---|---|---|
| Go / Rust | Very fast (~10 ms) | Best for latency-sensitive workloads |
| Node.js (ESM) | Fast (~100–200 ms) | Keep bundle small; avoid large deps |
| Python | Medium (~200–500 ms) | Use Lambda layers for heavy deps |
| JVM (Java/Kotlin) | Slow (1–5 s) | Use GraalVM native image or SnapStart |
Mitigate cold starts for latency-critical functions:
# serverless.yml or SAM template
Properties:
ProvisionedConcurrencyConfig:
ProvisionedConcurrentExecutions: 2 # keeps N instances warm
Use provisioned concurrency only where latency SLAs justify the cost.
Step 3 — Event Sources
| Trigger | Pattern | Notes |
|---|---|---|
| API Gateway / ALB | Synchronous HTTP | Return response within 29 s |
| SQS | Async batch processing | Set visibility timeout > max duration |
| EventBridge | Event-driven, fan-out | Ideal for domain events |
| S3 | File processing | Trigger on ObjectCreated, filter by prefix |
| DynamoDB Streams | Change data capture | Process in order per partition key |
| Scheduled (EventBridge) | Cron jobs | Use for periodic maintenance tasks |
Step 4 — IAM Least Privilege
Every function gets its own IAM execution role. Grant only what the function needs:
{
"Statement": [
{
"Effect": "Allow",
"Action": ["dynamodb:GetItem", "dynamodb:PutItem"],
"Resource": "arn:aws:dynamodb:us-east-1:123456789:table/orders"
},
{
"Effect": "Allow",
"Action": ["sqs:SendMessage"],
"Resource": "arn:aws:sqs:us-east-1:123456789:fulfillment-queue"
}
]
}
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 · 135 lines · 62 tokens per session scan A 059df60bcd89
serverless-architecture is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 1,177 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-08-31.
Other skills, from other repositories
architecture-paradigm-serverless
Applies serverless FaaS patterns for event-driven workloads. Use when designing bursty workloads with minimal infrastructure and pay-per-execution cost model.
serverless
Advanced serverless deployment and cold-start optimization skill.
hatch3r-scalability-verify
Scalability verification gate before commit/release — stateless-handler ratio, back-pressure patterns, idempotency-key adoption, queue-based offloading, pool sizing, bulkheads, load-test pass at target scale.
aws-cli
CLI-first AWS orchestration skill for Lambda, ECS/Fargate, and S3 workflows rooted in .☁️ runbooks.
aws-cloud-architecture
Comprehensive guide to AWS cloud architecture covering compute, storage, databases, networking, security, serverless, and cost optimization with production-ready patterns.
modal-serverless-gpu
Run approved CPU or GPU work through OpenScience computejob on the user's configured Modal account. Use for isolated scientific scripts, dependency provisioning, durable outputs, logs, status, cancellation, and recovery. Never invoke the Modal SDK or CLI directly.