Awesome Claude Code Toolkit is a curated collection of extensions and configuration for Claude Code, including agents, skills, commands, plugins, hooks, rules, templates, MCP configurations, and companion apps. It is for Claude Code users who want ready-made workflows and integrations for different development tasks. The catalogue add-ons are selected components from this toolkit.
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.
git clone --depth 1 https://github.com/rohitg00/awesome-claude-code-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/commands/rohitg00/awesome-claude-code-toolkit/setup-lambda)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/setup-lambda"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/setup-lambda/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/commands/rohitg00/awesome-claude-code-toolkit/setup-lambda"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/setup-lambda.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.00000 | $0.00320 |
| Opus 5.5 | $0.00000 | $0.00128 |
| Sonnet 5.5 | $0.00000 | $0.00064 |
| Haiku 4.5 | $0.00000 | $0.00032 |
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 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.
What it actually says
/setup-lambda - Setup AWS Lambda Function
Configure and deploy an AWS Lambda function with proper settings.
Steps
- Ask the user for the function name, runtime (Node.js, Python, Go), and trigger type
- Create the Lambda function handler file with the appropriate template
- Generate the IAM role and policy with least-privilege permissions
- Configure environment variables for the function
- Set memory allocation (default 256MB) and timeout (default 30s) based on workload
- Configure the trigger: API Gateway, S3 event, SQS queue, EventBridge schedule, or DynamoDB stream
- Set up VPC configuration if the function needs database or internal service access
- Add CloudWatch log group with appropriate retention period (default 30 days)
- Configure dead letter queue for failed invocations
- Create the deployment package or container image configuration
- Generate the IaC definition (CloudFormation, SAM, or CDK) for the Lambda
- 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
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 · 29 lines · 0 tokens per session scan A 461f1e92f6a9
setup-lambda is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,711 stars, last pushed 5mo 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.
Other commands, from other repositories
rclone_mkdir
Make the path if it doesn't already exist.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.