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/organize)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/organize"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/organize/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/organize"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/organize.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.00301 |
| Opus 5 | $0.00000 | $0.00151 |
| Sonnet 5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
organize 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 5d 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
/organize - Organize Imports
Sort, group, and clean up import statements across the project.
Steps
- Detect the project language and import style (ES modules, CommonJS, Python, Go, etc.)
- Read the project's linting configuration for import ordering rules
- Scan target files for all import statements
- Remove duplicate imports that import the same module
- Remove unused imports that are not referenced in the file body
- Group imports into standard categories: built-in, external, internal, relative, type-only
- Sort imports alphabetically within each group
- Add blank lines between import groups for visual separation
- Convert wildcard imports to named imports where only specific exports are used
- Merge multiple imports from the same module into a single import statement
- Apply consistent quote style (single or double) matching project conventions
- Run the linter to verify the organized imports pass all rules
Rules
- Follow the project's existing import ordering convention if one exists
- Standard grouping order: built-in, external packages, internal aliases, relative paths
- Type-only imports should be grouped separately (TypeScript)
- Do not reorder imports if the order has side effects (CSS imports, polyfills)
- Keep namespace imports when they are used extensively (more than 5 references)
- Use path aliases from tsconfig.json or webpack config when available
- Process one file at a time to allow incremental review
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.
- 5d ago First seen · 29 lines · 0 tokens per session scan A c754a8b3a1bf
organize is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,598 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 301 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
check-todos
List outstanding todos and select one to work on.
run-prompt
Delegate one or more prompts to fresh sub-task contexts with parallel or sequential execution.
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.