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/generate-manifest)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/generate-manifest"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/generate-manifest.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.00308 |
| Opus 5 | $0.00000 | $0.00154 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
generate-manifest 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 3d 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
Generate production-ready Kubernetes manifests from application configuration.
Steps
- Analyze the application:
- Read Dockerfile for container port, health check, and entrypoint.
- Read environment variable requirements from
.env.example. - Detect service dependencies from docker-compose or config files.
- Generate manifests:
- Namespace definition.
- Deployment with resource limits, probes, and rolling update strategy.
- Service (ClusterIP for internal, LoadBalancer for external).
- ConfigMap for non-sensitive configuration.
- Secret template for sensitive values.
- Ingress with TLS if external access is needed.
- HPA for auto-scaling based on CPU/memory.
- Add Kustomize base and overlays for dev/staging/production.
- Validate manifests:
kubectl apply --dry-run=client -f .. - Write files to
k8s/ordeploy/directory.
Format
apiVersion: apps/v1
kind: Deployment
metadata:
name: <app>
labels:
app.kubernetes.io/name: <app>
app.kubernetes.io/version: <version>
Rules
- Always set CPU and memory requests and limits.
- Include readiness and liveness probes for every container.
- Use
app.kubernetes.io/label conventions. - Never hardcode secrets; use Secret resources or external-secrets operator.
- Set
securityContextwith non-root user and read-only filesystem where possible.
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.
- 3d ago First seen · 40 lines · 0 tokens per session scan A 4bcedca0012f
generate-manifest 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 308 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
create-docker-mcp-tunnel
Stand up an Anthropic MCP tunnel locally with Docker Compose so Claude can call a private MCP server (manual-credentials quickstart).
vios-architecture
Explain the VIOS stream-processor and sensor microservice deployment architecture: containers, ingress, RTSP, file-upload, WebRTC, Envoy, SDR, routing, and event flow.
deployment
Basic production deployment setup for FastAPI applications.
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.