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/benchmark)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/benchmark"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/benchmark/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/benchmark"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/benchmark.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.00295 |
| Opus 5.5 | $0.00000 | $0.00118 |
| Sonnet 5.5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
benchmark 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
/benchmark - Benchmark API Endpoints
Run performance benchmarks against API endpoints.
Steps
- Ask the user for the target endpoint URL and HTTP method
- Configure the request: headers, authentication, request body, query parameters
- Run a warmup phase: 10 requests to prime caches and connections
- Execute the benchmark with configurable parameters:
- Concurrent connections (default: 10)
- Total requests (default: 1000)
- Duration-based (alternative to request count)
- Capture per-request metrics: response time, status code, response size
- Calculate statistics: min, max, mean, median, p95, p99 response times
- Calculate throughput: requests per second, bytes per second
- Record error rate and categorize errors by status code
- Detect performance degradation over the benchmark duration
- Compare against SLA targets if defined
- Save raw results in JSON format for further analysis
- Present a formatted summary with key metrics and pass/fail status
Rules
- Always include a warmup phase before measuring
- Use keep-alive connections to simulate realistic client behavior
- Record and report all HTTP status codes, not just 200s
- Include connection time separately from response time
- Do not benchmark production endpoints without explicit permission
- Run from a network location representative of actual users
- Report the server and client environment for reproducibility
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 · 32 lines · 0 tokens per session scan A 6978226bf945
benchmark is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,733 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 295 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
create-slash-command
Create a new slash command following best practices and patterns.
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.