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/report)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/report"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/report/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/report"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/report.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.00017 | $0.00401 |
| Opus 5.5 | $0.00007 | $0.00160 |
| Sonnet 5.5 | $0.00003 | $0.00080 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
report 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
Generate a project analytics report covering code quality, velocity, and health metrics.
Steps
- Gather git statistics:
git shortlog -sn --no-mergesfor contributor activity.git log --format='%ai' --since='30 days ago'for commit frequency.git diff --stat HEAD~50for recent change volume.
- Analyze code quality metrics:
- Lines of code by language using file extensions.
- Test-to-code ratio (test files vs source files).
- Average file size and function length.
- TODO/FIXME/HACK comment count.
- Check dependency health:
- Total dependencies (direct and transitive).
- Outdated packages count.
- Known vulnerability count.
- Measure test health:
- Run test suite and capture pass/fail ratio.
- Calculate approximate coverage if coverage tool exists.
- Assess documentation coverage:
- README completeness check.
- API documentation presence.
- Inline documentation density.
- Compile findings into a structured report.
Format
Project Health Report - <date>
Code: <N> files, <N> LOC across <N> languages
Tests: <N> tests, <pass rate>% passing
Deps: <N> direct, <N> outdated, <N> vulnerable
Activity: <N> commits in last 30 days by <N> contributors
Score: <A/B/C/D/F>
Top issues:
1. <most impactful issue>
2. <second most impactful>
Rules
- Use objective metrics, not subjective assessments.
- Compare against industry benchmarks where possible.
- Highlight trends (improving/declining) over the last 30 days.
- Keep the report under 100 lines for quick consumption.
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 · 54 lines · 17 tokens per session scan A e5dc36689e26
report is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,713 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 401 once invoked, about $0.0001 per session on Opus 5.5. 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-refactor
(Conductor) Refactor a file or module for clarity and simplicity.
create-prompt
Create a new prompt that another Claude can execute.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.