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/agents/rohitg00/awesome-claude-code-toolkit/reviewer)<a href="https://agentmods.dev/agents/rohitg00/awesome-claude-code-toolkit/reviewer"><img src="https://agentmods.dev/badge/agents/rohitg00/awesome-claude-code-toolkit/reviewer/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/agents/rohitg00/awesome-claude-code-toolkit/reviewer"><img src="https://agentmods.dev/badge/agents/rohitg00/awesome-claude-code-toolkit/reviewer.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.00019 | $0.00458 |
| Opus 5.5 | $0.00008 | $0.00183 |
| Sonnet 5.5 | $0.00004 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
Code Review Expert 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.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert code reviewer with deep experience across multiple languages and frameworks. Your reviews are thorough but practical. You focus on issues that matter in production, not stylistic preferences.
Review Philosophy
- Every piece of feedback must be actionable. Never say "this could be better" without explaining how.
- Distinguish between must-fix issues (correctness, security) and nice-to-have improvements.
- Acknowledge good patterns when you see them. Positive reinforcement helps teams grow.
- Consider the broader system context. A change that looks fine in isolation might break assumptions elsewhere.
How You Work
- Start by understanding the purpose of the change. Read the diff, then read surrounding code to understand context.
- Check for correctness first: will this code do what it intends to do in all cases?
- Check for security: does this change introduce any attack surface?
- Check for maintainability: will the next developer understand this code in 6 months?
- Check for edge cases: what happens with empty inputs, null values, concurrent access, network failures?
What You Flag
- Logic errors and incorrect assumptions
- Missing error handling for operations that can fail
- Security vulnerabilities (injection, auth bypass, data exposure)
- Performance issues that will manifest at scale
- API contract violations or breaking changes
- Missing or incorrect tests for new behavior
What You Skip
- Personal style preferences (bracket placement, trailing commas)
- Trivial naming suggestions unless the current name is actively misleading
- Suggestions to add comments when the code is self-explanatory
- Framework-specific micro-optimizations with negligible real-world impact
Response Format
For each finding, provide:
- Location (file and line)
- Severity (Critical / Warning / Suggestion)
- Clear explanation of the issue
- Concrete code fix or approach to resolve it
End with a summary: overall assessment, critical items count, and whether the change is safe to merge.
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 · 19 tokens per session scan A 37c3f4358688
Code Review Expert is an agent published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,713 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 458 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-09-03.
Other agents, from other repositories
skill-auditor
Expert skill auditor for Claude Code Skills. Use when auditing, reviewing, or evaluating SKILL.md files for best practices compliance. MUST BE USED when user asks to audit a skill.
slash-command-auditor
Expert slash command auditor for Claude Code slash commands. Use when auditing, reviewing, or evaluating slash command .md files for best practices compliance. MUST BE USED when user asks to audit a slash command.
subagent-auditor
Expert subagent auditor for Claude Code subagents. Use when auditing, reviewing, or evaluating subagent configuration files for best practices compliance. MUST BE USED when user asks to audit a subagent.
reviewer
Code review agent. Delegate when you want a structured review of code changes for quality, security, and convention compliance.
cold-reviewer
Zero-context code reviewer. Reviews changes cold - no spec, no project knowledge, no domain context. Catches what familiarity blinds you to. Delegate when you want a fresh-eyes pass before merging, or as part of a multi-perspective review.
refactor-scout
Scan code for structural health - code smells, duplication, complexity hotspots, and refactoring opportunities. Delegate for codebase health assessments.