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/analyze-complexity)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/analyze-complexity"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/analyze-complexity/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/analyze-complexity"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/analyze-complexity.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.00301 |
| Opus 5.5 | $0.00000 | $0.00120 |
| Sonnet 5.5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
analyze-complexity 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
/analyze-complexity - Analyze Code Complexity
Calculate cyclomatic complexity and identify overly complex functions.
Steps
- Detect the project language to select the appropriate complexity analysis tool
- Scan all source files excluding tests, vendor, and generated code
- Calculate cyclomatic complexity for each function and method
- Calculate cognitive complexity as a secondary metric
- Identify functions exceeding the threshold (default: cyclomatic > 10)
- Rank the top 20 most complex functions by complexity score
- For each complex function, identify the complexity drivers: nested conditionals, switch cases, loops
- Calculate file-level complexity averages and identify the most complex files
- Compare against industry benchmarks: low (1-5), moderate (6-10), high (11-20), very high (21+)
- Generate a formatted report with function name, file, line, complexity score
- Suggest specific refactoring strategies for the top 5 most complex functions
- Save the report and track complexity trends over time
Rules
- Use cyclomatic complexity as the primary metric
- Include cognitive complexity as a complementary measure
- Exclude generated code, migrations, and configuration files
- Threshold of 10 for warnings, 20 for critical flags
- Consider function length alongside complexity (long + complex = priority)
- Do not count simple switch/case with returns as highly complex
- Report both absolute values and percentile rankings
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 · 29 lines · 0 tokens per session scan A 9f4f92d34301
analyze-complexity is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,721 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 301 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
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.