setup-lambda

A command for setting up and deploying an AWS Lambda function, a small program that runs in response to events without managing a server. It creates the function configuration, permissions, infrastructure definition, and documentation.

In plain words
What is it for?
Use it to configure a Lambda triggered by an API, file upload, queue, schedule, database stream, or other supported AWS event, with environment variables, logs, networking, and infrastructure as code.
Why use it?
It organizes the many deployment, security, logging, and failure-handling settings that are easy to miss when creating a Lambda function manually.

Command

Install

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.

agentmods
npx agentmods add commands/rohitg00/awesome-claude-code-toolkit/setup-lambda
Clone the repo
git clone --depth 1 https://github.com/rohitg00/awesome-claude-code-toolkit
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 320 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00320
Opus 5 $0.00000 $0.00160
Sonnet 5 $0.00000 $0.00064
Haiku 4.5 $0.00000 $0.00032

Measured 2d ago against content hash 461f1e92f6a9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

setup-lambda 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 2d 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.

plugins/aws-helper/commands/setup-lambda.md · 29 lines

What it actually says

/setup-lambda - Setup AWS Lambda Function

Configure and deploy an AWS Lambda function with proper settings.

Steps

  1. Ask the user for the function name, runtime (Node.js, Python, Go), and trigger type
  2. Create the Lambda function handler file with the appropriate template
  3. Generate the IAM role and policy with least-privilege permissions
  4. Configure environment variables for the function
  5. Set memory allocation (default 256MB) and timeout (default 30s) based on workload
  6. Configure the trigger: API Gateway, S3 event, SQS queue, EventBridge schedule, or DynamoDB stream
  7. Set up VPC configuration if the function needs database or internal service access
  8. Add CloudWatch log group with appropriate retention period (default 30 days)
  9. Configure dead letter queue for failed invocations
  10. Create the deployment package or container image configuration
  11. Generate the IaC definition (CloudFormation, SAM, or CDK) for the Lambda
  12. Document the function: purpose, trigger, environment variables, and IAM permissions

Rules

  • Always use least-privilege IAM policies; never use AdministratorAccess
  • Set appropriate memory and timeout; do not use maximum values by default
  • Include error handling and structured logging in the handler template
  • Configure reserved concurrency if the function should be rate-limited
  • Use environment variables for configuration, not hardcoded values
  • Enable X-Ray tracing for production functions
  • Add tags for cost allocation: team, project, environment
Changes

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.

  1. 2d ago First seen · 29 lines · 0 tokens per session scan A 461f1e92f6a9

Subscribe to this mod's changes

setup-lambda is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,570 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 320 tokens. 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-30.