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/dockerfile)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/dockerfile"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/dockerfile/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/dockerfile"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/dockerfile.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.00697 |
| Opus 5.5 | $0.00000 | $0.00279 |
| Sonnet 5.5 | $0.00000 | $0.00139 |
| Haiku 4.5 | $0.00000 | $0.00070 |
Grade A, and why
dockerfile 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/deploy-pilot:dockerfile
Generate an optimized multi-stage Dockerfile for the current project.
Process
-
Detect the project type and runtime:
- Check for
package.json(Node.js),requirements.txt/pyproject.toml(Python),go.mod(Go),Cargo.toml(Rust),pom.xml/build.gradle(Java) - Identify the framework (Next.js, FastAPI, Gin, Actix, Spring Boot, etc.)
- Read the existing entrypoint script or start command
- Check for
-
Select the appropriate base image:
- Use official slim/alpine variants for smaller image sizes
- Pin to a specific version tag, never use
latest - For Node.js:
node:22-alpinefor runtime,node:22for build - For Python:
python:3.12-slimfor runtime - For Go:
golang:1.23-alpinefor build,gcr.io/distroless/static-debian12for runtime - For Rust:
rust:1.82-slimfor build,debian:bookworm-slimfor runtime
-
Structure the Dockerfile with these stages:
Stage 1: Dependencies
- Copy only dependency manifests (package.json, go.sum, Cargo.lock, etc.)
- Install dependencies in a cached layer
- This stage changes only when dependencies change, maximizing cache hits
Stage 2: Build
- Copy source code
- Run the build command (compile, transpile, bundle)
- Run tests if a
--with-testsflag is specified - Prune dev dependencies after build
Stage 3: Runtime
- Start from a minimal base image
- Copy only the built artifacts and production dependencies
- Set a non-root user for security
- Configure health check with appropriate endpoint or command
- Set resource limits via labels where applicable
- Define the entrypoint and default command
- Apply these optimizations:
- Order COPY instructions from least to most frequently changed
- Use
.dockerignorepatterns: suggest creating one if missing - Set
NODE_ENV=productionor equivalent environment variables - Use
COPY --from=buildto minimize final image layers - Add
LABELinstructions for maintainer, version, and description - Set
EXPOSEfor the application port - Use
tiniordumb-initas PID 1 for proper signal handling in Node.js
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 · 65 lines · 0 tokens per session scan A 232dc937265f
dockerfile is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,717 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 697 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-09-03.
Other commands, from other repositories
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.