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/reviewgit 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/review)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/review"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/review.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.00021 | $0.00604 |
| Opus 5 | $0.00010 | $0.00302 |
| Sonnet 5 | $0.00004 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
review 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/code-guardian:review
Perform a thorough code review of the current uncommitted changes or a specified file/directory.
Process
-
Gather the changes to review:
- Run
git difffor unstaged changes andgit diff --cachedfor staged changes - If a specific file or directory is provided as an argument, focus the review there
- If no changes exist, review the most recent commit with
git diff HEAD~1
- Run
-
Analyze each changed file across these dimensions:
Correctness
- Logic errors, off-by-one mistakes, incorrect boolean conditions
- Unhandled null/undefined values and missing error boundaries
- Race conditions in async code, missing awaits, unhandled promise rejections
- Incorrect type assertions or unsafe casts
Security
- User input flowing to SQL queries, shell commands, or file paths without sanitization
- Hardcoded credentials, API keys, tokens, or connection strings
- Missing authentication or authorization checks on new endpoints
- Unsafe deserialization of external data
Performance
- N+1 query patterns in database access
- Unnecessary re-renders in React components (missing memoization, unstable references)
- Unbounded data fetching without pagination or limits
- Synchronous blocking operations on hot paths
- Memory leaks from unclosed resources, event listeners, or subscriptions
Design
- Single Responsibility violations: functions or classes doing too many things
- Tight coupling between modules that should be independent
- Missing abstractions where patterns repeat three or more times
- Public API surface area: are new exports intentional and well-designed?
Readability
- Variable and function names that obscure intent
- Deeply nested conditionals that should be flattened or extracted
- Magic numbers or strings that should be named constants
- Missing or misleading type annotations
- Classify each finding by severity:
- CRITICAL - Will cause bugs, data loss, or security vulnerabilities in production
- WARNING - Likely to cause issues under certain conditions or during maintenance
- SUGGESTION - Improvement opportunity that is not urgent
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 · 72 lines · 21 tokens per session scan A 0597b8aaee75
review is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,585 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 604 once invoked, about $0.0001 per session on Opus 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-09-03.
Other commands, from other repositories
create-prompt
Create a new prompt that another Claude can execute.
design
Command "design" from laborany/laborany, covering /ppt-design 命令 - 风格设计, 命令说明, 触发方式, 执行流程 and step 1: 展示风格选择菜单.
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.
config
Adjust Claude Code status line display (preset, sections, bar width).
enhance
Analyze the current copy issues and enhance it.
ci
Analyze Github Actions logs and fix issues.