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.
npx agentmods add commands/rohitg00/awesome-claude-code-toolkit/configure-s3git 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/configure-s3)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/configure-s3"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/configure-s3.svg" alt="Measured on agentmods" 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.00299 |
| Opus 5 | $0.00000 | $0.00150 |
| Sonnet 5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
configure-s3 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 7d 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
/configure-s3 - Configure AWS S3 Bucket
Create and configure an S3 bucket with security best practices.
Steps
- Ask the user for the bucket purpose: static hosting, file storage, backups, logs
- Generate a globally unique bucket name following naming conventions
- Configure bucket policy based on access requirements (private, public-read, CDN-only)
- Enable server-side encryption (AES-256 or KMS) by default
- Block all public access unless explicitly required for static hosting
- Configure CORS rules if the bucket serves content to web applications
- Set up lifecycle rules: transition to Glacier after 90 days, expire after 365 days
- Enable versioning for data protection and accidental deletion recovery
- Configure access logging to a separate logging bucket
- Set up event notifications for object creation or deletion if needed
- Generate the IaC definition (CloudFormation or CDK) for the bucket
- Document bucket configuration: name, region, access policy, encryption, lifecycle
Rules
- Always block public access unless the user explicitly requires public hosting
- Enable encryption at rest for all buckets
- Use bucket policies over ACLs (ACLs are legacy)
- Enable versioning for any bucket containing user data or important files
- Configure lifecycle rules to manage storage costs
- Set up access logging for compliance and audit requirements
- Use regional bucket names to avoid global namespace conflicts
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.
- 7d ago First seen · 29 lines · 0 tokens per session scan A b1a8e2de2871
configure-s3 is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,593 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 299 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
build-mcp
Build a remote MCP server on Cloudflare using McpAgent.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.