tree-shake

tree-shake is a command for coding agents from rohitg00/awesome-claude-code-toolkit. It costs 13 tokens per session (291 once invoked), scanned A, original, Apache-2.0.

A build-analysis command that finds changes which can make tree shaking remove unused code from JavaScript bundles. Tree shaking is the process of excluding unused modules from the files shipped to users.

In plain words
What is it for?
Use it to inspect sideEffects settings, namespace or CommonJS imports, barrel files, and package formats, then rebuild and compare the resulting size.
Why use it?
It helps reduce bundle size by identifying import patterns, package settings, and module structures that keep unused code in the build.

Command

Part of the bundle-analyzer plugin — 2 commands shipped together

Install

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.

agentmods
npx agentmods add commands/rohitg00/awesome-claude-code-toolkit/tree-shake
Clone the repo
git clone --depth 1 https://github.com/rohitg00/awesome-claude-code-toolkit

Or install bundle-analyzer, the plugin that ships this one along with the rest of its 2 commands.

Wrote 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.

agentmods badge for tree-shake

README.md
[![agentmods](https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/tree-shake.svg)](https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/tree-shake)
Your own site
<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="Measured on agentmods" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 291 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.00291
Opus 5 $0.00006 $0.00146
Sonnet 5 $0.00003 $0.00058
Haiku 4.5 $0.00001 $0.00029

Measured 4d ago against content hash 87c60a423091, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

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.

plugins/bundle-analyzer/commands/tree-shake.md · 34 lines

What it actually says

/tree-shake - Optimize Tree Shaking

Improve tree shaking effectiveness to reduce bundle size.

Steps

  1. Analyze the current build configuration for tree shaking settings
  2. Check package.json for sideEffects field configuration
  3. Identify imports that prevent tree shaking: namespace imports, CommonJS requires
  4. Find barrel files (index.ts re-exports) that bundle entire modules
  5. Check for packages that do not support tree shaking (no ES modules)
  6. Convert namespace imports to named imports where possible
  7. Add sideEffects: false to package.json if all modules are pure
  8. Configure the bundler to mark specific files as side-effect-free
  9. Replace non-tree-shakeable packages with tree-shakeable alternatives
  10. Split barrel files into direct imports for large modules
  11. Rebuild and measure the size difference
  12. 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
Changes

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.

  1. 4d ago First seen · 34 lines · 13 tokens per session scan A 87c60a423091

Subscribe to this mod's changes

tree-shake is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,585 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 291 once invoked, about $0.0001 per session on Opus 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.