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/k8s-manifest)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/k8s-manifest"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/k8s-manifest/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/k8s-manifest"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/k8s-manifest.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.00740 |
| Opus 5 | $0.00000 | $0.00370 |
| Sonnet 5 | $0.00000 | $0.00148 |
| Haiku 4.5 | $0.00000 | $0.00074 |
Grade A, and why
k8s-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 5d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/deploy-pilot:k8s-manifest
Generate production-ready Kubernetes manifests for the current application.
Process
-
Gather application details:
- Read the Dockerfile or build config to determine the container image and port
- Check for existing k8s manifests in
k8s/,deploy/,manifests/, orkubernetes/directories - Identify environment variables from
.env.exampleor the application config - Determine resource requirements based on the application type
-
Generate a Deployment manifest:
- Set
replicas: 2as the default for high availability - Configure rolling update strategy with
maxSurge: 1andmaxUnavailable: 0 - Set resource requests and limits:
- Web apps: 128Mi memory request, 256Mi limit, 100m CPU request, 500m limit
- APIs: 256Mi memory request, 512Mi limit, 200m CPU request, 1000m limit
- Workers: 512Mi memory request, 1Gi limit, 250m CPU request, 1000m limit
- Add liveness and readiness probes:
- HTTP probe for web services (GET /healthz)
- TCP probe for non-HTTP services
- Set initialDelaySeconds, periodSeconds, and failureThreshold appropriately
- Mount environment variables from ConfigMap and secrets from Secret
- Set security context: runAsNonRoot, readOnlyRootFilesystem, drop all capabilities
- Add pod disruption budget for graceful scaling
- Set
-
Generate a Service manifest:
- ClusterIP service for internal communication
- Match the deployment selector labels
- Map the container port to the service port
-
Generate an Ingress manifest (if the app is externally accessible):
- Use the
networking.k8s.io/v1API version - Configure TLS with a placeholder for cert-manager cluster issuer annotation
- Set appropriate path type (Prefix for SPAs, Exact for APIs)
- Include a placeholder hostname that the user should customize
- Use the
-
Generate supporting resources:
- ConfigMap for non-sensitive environment variables
- Secret manifest (with placeholder values) for sensitive configuration
- HorizontalPodAutoscaler targeting 70% CPU utilization, scaling 2-10 replicas
- NetworkPolicy restricting ingress to only the necessary ports
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.
- 5d ago First seen · 69 lines · 0 tokens per session scan A 926e98beaf0c
k8s-manifest is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,598 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 740 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.