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/test-endpoint)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/test-endpoint"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/test-endpoint/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/test-endpoint"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/test-endpoint.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.00410 |
| Opus 5.5 | $0.00000 | $0.00164 |
| Sonnet 5.5 | $0.00000 | $0.00082 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
test-endpoint scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Send the request using `curl` or `fetch`. What it actually says
Test an API endpoint with various request scenarios and validate responses.
Steps
- Parse the endpoint specification:
- URL, HTTP method, headers, authentication.
- Request body (JSON, form data, multipart).
- Expected response status and body schema.
- Generate test scenarios:
- Happy path: Valid request with expected response.
- Validation: Missing required fields, invalid types, out-of-range values.
- Auth: Missing token, expired token, insufficient permissions.
- Edge cases: Empty body, very large payload, special characters.
- Idempotency: Repeated identical requests produce consistent results.
- Execute each test:
- Send the request using
curlorfetch. - Capture response status, headers, body, and timing.
- Validate against expected results.
- Send the request using
- Check response quality:
- Correct content type header.
- Consistent error format across failure cases.
- Proper HTTP status codes (not 200 for errors).
- No sensitive data in error responses.
- Generate a test summary with pass/fail for each scenario.
Format
API Test: <METHOD> <endpoint>
| Scenario | Status | Expected | Actual | Time | Result |
|----------|--------|----------|--------|------|--------|
| Valid request | 200 | 200 | 200 | 45ms | PASS |
| Missing auth | 401 | 401 | 401 | 12ms | PASS |
| Invalid body | 400 | 400 | 500 | 23ms | FAIL |
Pass: <N>/<total>
Issues: <list of failures>
Rules
- Test authentication and authorization for every endpoint.
- Verify error responses do not leak stack traces or internal details.
- Check that CORS headers are set correctly for browser-accessible APIs.
- Test with realistic payloads, not minimal test data.
- Verify rate limiting works as documented.
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 · 48 lines · 0 tokens per session scan A d35b92ba4875
test-endpoint is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,729 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 410 tokens. A static security scan graded it A with 1 finding (makes network calls). 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-test
(Conductor) Analyze coverage gaps and write missing tests.
help
Explain what loop-virtuoso does, its two modes, and its commands.
testing
Comprehensive testing setup for FastAPI applications with pytest and async support.
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.