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/debug)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/debug"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/debug/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/debug"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/debug.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.00335 |
| Opus 5.5 | $0.00000 | $0.00134 |
| Sonnet 5.5 | $0.00000 | $0.00067 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
debug 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.
What it actually says
Systematically debug an issue by analyzing symptoms, forming hypotheses, and testing them.
Steps
- Gather the bug report: error message, stack trace, reproduction steps, expected vs actual behavior.
- Identify the entry point where the issue manifests (endpoint, UI action, CLI command).
- Trace the execution path from entry to error:
- Read the code path that handles the triggering action.
- Check for recent changes in the affected files:
git log --oneline -10 -- <file>. - Look for related error handling or edge cases.
- Form hypotheses ranked by likelihood:
- Data issue: unexpected null, wrong type, missing field.
- Logic error: incorrect condition, off-by-one, wrong operator.
- State issue: race condition, stale cache, missing initialization.
- Environment: missing config, version mismatch, network failure.
- Test each hypothesis:
- Add targeted logging or breakpoints.
- Write a minimal reproduction test case.
- Check edge cases around the failure point.
- Implement the fix and verify it resolves the issue.
- Add a regression test that would catch the bug if reintroduced.
Format
Bug: <description>
Root Cause: <what actually went wrong>
Fix: <what was changed>
Files: <list of modified files>
Test: <regression test added>
Rules
- Start with the simplest hypothesis before investigating complex causes.
- Never fix a bug without understanding the root cause.
- Always add a regression test for the fix.
- Check if the same bug pattern exists elsewhere in the codebase.
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 · 39 lines · 0 tokens per session scan A 899155c50712
debug is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,704 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 335 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
cc-debug
(Conductor) Systematically diagnose and fix a bug.
debug
Apply expert debugging methodology to investigate a specific issue.
triage
Triage a bug report (PDF / markdown / text) — extract the issues, prioritize, then run the fix pipeline per issue.
fix
Triage pasted logs/stacks into bugs findings and todos. Does not change application code unless the user confirms.
debug
Start systematic debugging methodology for investigating bugs and errors.
checklist
Generate a custom checklist for the current feature based on user requirements.