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/tree-shake)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/tree-shake"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/tree-shake/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/tree-shake"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/tree-shake.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.00013 | $0.00291 |
| Opus 5.5 | $0.00005 | $0.00116 |
| Sonnet 5.5 | $0.00003 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
tree-shake 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
/tree-shake - Optimize Tree Shaking
Improve tree shaking effectiveness to reduce bundle size.
Steps
- Analyze the current build configuration for tree shaking settings
- Check package.json for sideEffects field configuration
- Identify imports that prevent tree shaking: namespace imports, CommonJS requires
- Find barrel files (index.ts re-exports) that bundle entire modules
- Check for packages that do not support tree shaking (no ES modules)
- Convert namespace imports to named imports where possible
- Add sideEffects: false to package.json if all modules are pure
- Configure the bundler to mark specific files as side-effect-free
- Replace non-tree-shakeable packages with tree-shakeable alternatives
- Split barrel files into direct imports for large modules
- Rebuild and measure the size difference
- Report: modules eliminated, size reduction, remaining issues
Rules
- Never mark files with side effects as side-effect-free
- Verify that tree shaking does not remove needed code
- Prefer named imports over namespace imports for better tree shaking
- Check that all internal packages have proper ESM exports
- Do not break the public API of packages when restructuring exports
- Test the application thoroughly after tree shaking changes
- Document any sideEffects configuration with comments explaining why
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 · 34 lines · 13 tokens per session scan A 87c60a423091
tree-shake 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 adds 13 tokens to every session and 291 once invoked, about $0.0001 per session on Opus 5.5. 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
cc-refactor
(Conductor) Refactor a file or module for clarity and simplicity.
create-prompt
Create a new prompt that another Claude can execute.
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.