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/debug-podgit 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/debug-pod)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/debug-pod"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/debug-pod.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 | $0.00000 | $0.00374 |
| Opus 5 | $0.00000 | $0.00187 |
| Sonnet 5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
debug-pod 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 yesterday.
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
Debug a failing or unhealthy Kubernetes pod by analyzing events, logs, and configuration.
Steps
- Get pod status:
kubectl get pod <name> -n <namespace> -o wide. - Describe the pod for events and conditions:
kubectl describe pod <name> -n <namespace>. - Analyze the pod state:
- Pending: Check node resources, scheduling constraints, PVC binding.
- CrashLoopBackOff: Check container logs for startup errors.
- ImagePullBackOff: Verify image name, tag, and registry credentials.
- OOMKilled: Check memory limits vs actual usage.
- Running but unhealthy: Check probe configuration and endpoints.
- Fetch container logs:
kubectl logs <pod> -n <ns> --previousfor crash logs. - Check resource usage:
kubectl top pod <name> -n <namespace>. - Verify configuration:
- ConfigMaps and Secrets are mounted correctly.
- Environment variables are set.
- Service account has required permissions.
- Suggest fixes based on the diagnosis.
Format
Pod: <name> in <namespace>
Status: <status>
Restarts: <count>
Node: <node-name>
Diagnosis:
Root cause: <description>
Evidence: <log lines or events>
Fix:
1. <action to take>
2. <verification command>
Rules
- Always check events first; they often reveal the root cause immediately.
- Fetch logs from the previous container instance for crash analysis.
- Check node-level issues if multiple pods on the same node are affected.
- Verify DNS resolution if the pod cannot reach other services.
- Check RBAC permissions if the pod gets authorization errors.
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.
- yesterday First seen · 45 lines · 0 tokens per session scan A 0f7adb953e2e
debug-pod is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,587 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 374 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
brainstorm
You are a Solution Brainstormer, an elite software engineering expert who specializes in system architecture design and technical decision-making. Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs.
ci
Analyze Github Actions logs and fix issues.
config
Adjust Claude Code status line display (preset, sections, bar width).
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.