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/generate-docs)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/generate-docs"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/generate-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.00642 |
| Opus 5 | $0.00000 | $0.00321 |
| Sonnet 5 | $0.00000 | $0.00128 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
generate-docs 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 3d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/doc-forge:generate-docs
Generate comprehensive documentation for the current project or a specified module.
Process
-
Survey the project to understand its architecture:
- Read the entry point (main.ts, index.js, app.py, main.go, src/lib.rs)
- Identify the module structure and public API surface
- Check for existing documentation (docs/ directory, JSDoc, docstrings, rustdoc)
- Read package.json, pyproject.toml, or Cargo.toml for project metadata
-
Generate documentation for each public module:
Module Overview
- Purpose: one paragraph explaining what this module does and when to use it
- Dependencies: what this module requires and what depends on it
- Architecture notes: key design decisions and patterns used
Function/Method Documentation
- For each exported function, document:
- Purpose in one sentence
- Parameters with types, descriptions, and default values
- Return type and description
- Exceptions/errors that can be thrown and under what conditions
- Usage example showing the most common invocation
- Edge cases: behavior with null inputs, empty collections, boundary values
Type/Interface Documentation
- For each exported type, document:
- Purpose and when to use this type
- Each field with its type, description, and constraints
- Relationships to other types (extends, implements, references)
- Construction patterns (factory functions, builders, constructors)
Configuration Documentation
- Environment variables with descriptions, types, defaults, and required/optional status
- Configuration file formats with annotated examples
- Feature flags and their effects on behavior
-
Generate usage examples:
- Quick start: minimal code to get the module working
- Common patterns: 3-5 typical use cases with complete code snippets
- Advanced usage: composition with other modules, custom configuration
- Error handling: how to properly handle failures from this module
-
Create a table of contents linking all documented modules.
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.
- 3d ago First seen · 69 lines · 0 tokens per session scan A dba60ae450fd
generate-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 642 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-09-03.
Other commands, from other repositories
create-prompt
Create a new prompt that another Claude can execute.
design
A command for choosing or defining the visual style of a PowerPoint presentation, including its colors, fonts, and page layouts. It offers preset styles, custom brand settings, and recommendations based on the presentation topic.
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.