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 j4flmao/agent-skills --skill serverlessgit clone --depth 1 https://github.com/j4flmao/agent-skillsWrote 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/j4flmao/agent-skills/serverless)<a href="https://agentmods.dev/skills/j4flmao/agent-skills/serverless"><img src="https://agentmods.dev/badge/skills/j4flmao/agent-skills/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/j4flmao/agent-skills/serverless"><img src="https://agentmods.dev/badge/skills/j4flmao/agent-skills/serverless.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.00013 | $0.00813 |
| Opus 5 | $0.00006 | $0.00407 |
| Sonnet 5 | $0.00003 | $0.00163 |
| Haiku 4.5 | $0.00001 | $0.00081 |
Grade A, and why
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 6d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Serverless Mastery
Purpose
Comprehensive serverless architecture management, focusing on AWS Lambda cold-start mitigation, Terraform IaC provisioning, and highly scalable event-driven patterns.
Core Principles
- Minimize deployment package size to reduce cold start latency.
- Leverage provisioned concurrency for latency-sensitive endpoints.
- Optimize execution environments using Graviton and minimal runtimes.
- Apply principle of least privilege in IAM roles.
- Use Infrastructure as Code (Terraform) for reproducible environments.
Agent Protocol
- Triggers: "deploy lambda", "optimize cold start"
- Input Context Required: AWS credentials, source code, traffic patterns
- Output Artifact: Terraform plan, optimized deployment zip
- Response Formats:
{ "status": "deployed", "lambda_arn": "arn:aws:lambda:us-east-1:123456789012:function:my-func", "cold_start_est_ms": 120 }
Decision Matrix
Is workload latency-sensitive?
+-- Yes --> Use Provisioned Concurrency
+-- No --> Standard on-demand Lambda
Detailed Architectural Overview
[API Gateway] ---> [Lambda Function] ---> [DynamoDB]
(Graviton2/Python)
Workflow Steps
Phase 1: Analysis
- Inspect source
- Identify deps
- Measure size
- Check limits
Phase 2: Optimization
- Strip binaries
- Bundle code
- Set architecture
- Tune memory
Phase 3: IaC Generation
- Write main.tf
- Define variables.tf
- Setup outputs.tf
- Provider config
Phase 4: Deployment
- terraform init
- terraform plan
- terraform apply
- verify state
Phase 5: Validation
- Invoke lambda
- Measure latency
- Verify logs
- End-to-end test
Phase 6: Monitoring
- Setup CloudWatch
- Create alarms
- Dashboard config
- Set alerts
Extended Troubleshooting Guide
| Symptom | Primary Cause | Mitigation Action |
|---|---|---|
| Timeout | Cold start | Increase timeout or use provisioned concurrency |
| Missing Module | Bad bundling | Check deployment package contents |
| Access Denied | IAM role | Attach correct policies |
| Throttling | Concurrency limit | Request quota increase |
| High cost | Over-provisioned | Tune memory/concurrency |
| Missing logs | CW permissions | Add AWSLambdaBasicExecutionRole |
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.
- 6d ago First seen · 128 lines · 13 tokens per session scan A 777cbe21c785
serverless is a skill published in the GitHub repository j4flmao/agent-skills (22 stars, last pushed 3d ago), licensed MIT. It adds 13 tokens to every session and 813 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
cis-aws-compute-12.6
Ensure Lambda functions are not exposed to everyone.
cis-aws-compute-12.7
Ensure Lambda functions are referencing active execution roles.
cis-aws-compute-12.8
Ensure that Code Signing is enabled for Lambda functions.
cis-aws-compute-12.10
Ensure Lambda functions do not allow unknown cross account access via permission policies.
cis-aws-compute-12.11
Ensure that the runtime environment versions used for your Lambda functions do not have end of support dates.
cis-aws-compute-12.12
Ensure encryption in transit is enabled for Lambda environment variables.