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/api-docs)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/api-docs"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/api-docs.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.1 | $0.00000 | $0.00770 |
| Opus 5 | $0.00000 | $0.00385 |
| Sonnet 5 | $0.00000 | $0.00154 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
api-docs 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 4d 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.
- curl command for the most common use case How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/doc-forge:api-docs
Generate API reference documentation from source code annotations, types, and route definitions.
Process
-
Discover the API surface:
- Scan for route definitions, controller classes, or handler functions
- Read middleware chain to understand request preprocessing (auth, validation, parsing)
- Identify the response format conventions (JSON envelope, error structure, pagination)
- Check for existing API documentation (Swagger UI, Redoc, custom docs)
-
For each endpoint, extract and document:
Endpoint Header
- HTTP method and full URL path (including base path and version prefix)
- Brief description of what the endpoint does
- Authentication requirement (public, authenticated, admin-only)
- Rate limit tier if applicable
Request Documentation
- Path Parameters: name, type, description, example value, validation constraints
- Query Parameters: name, type, required/optional, default value, description, allowed values
- Headers: required custom headers beyond standard ones (Accept, Content-Type)
- Request Body: full schema with field descriptions, types, constraints, and example payload
- Mark required fields explicitly
- Document nested objects and arrays with their own field descriptions
- Include validation rules (min/max length, regex patterns, enum values)
Response Documentation
- For each possible status code:
- Status code and meaning in context
- Response body schema with field descriptions
- Complete example response payload
- Standard status codes to document:
- 200/201 for success
- 400 for validation errors (with example of error detail format)
- 401 for unauthenticated requests
- 403 for insufficient permissions
- 404 for resource not found
- 409 for conflict (duplicate creation, version mismatch)
- 429 for rate limit exceeded
- 500 for server errors (with error correlation ID format)
Code Examples
- curl command for the most common use case
- Language-specific examples if SDK libraries exist (JavaScript fetch, Python requests)
- WebSocket examples if the API includes real-time features
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.
- 4d ago First seen · 84 lines · 0 tokens per session scan A b6e087854dfc
api-docs is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,595 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 770 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-09-03.
Other commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.