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.
npx agentmods add commands/rohitg00/awesome-claude-code-toolkit/analyze-bundlegit 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/analyze-bundle)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/analyze-bundle"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/analyze-bundle.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 | $0.00015 | $0.00294 |
| Opus 5 | $0.00008 | $0.00147 |
| Sonnet 5 | $0.00003 | $0.00059 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
analyze-bundle 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.
What it actually says
/analyze-bundle - Analyze Frontend Bundle
Analyze JavaScript bundle size and identify optimization opportunities.
Steps
- Detect the build tool: webpack, Vite, Rollup, esbuild, or Parcel
- Run a production build with bundle analysis enabled
- Parse the bundle stats to identify all chunks and their sizes
- List the top 20 largest modules by gzipped size
- Identify duplicate packages included multiple times in the bundle
- Detect packages that could be replaced with smaller alternatives
- Calculate the total bundle size: raw, minified, and gzipped
- Break down the bundle by category: app code, node_modules, assets
- Check for source maps leaking to production builds
- Identify dynamic import opportunities for code splitting
- Compare against performance budgets if configured
- Generate a report with size breakdown, duplicates, and recommendations
Rules
- Always report gzipped sizes as that reflects actual transfer size
- Flag any single chunk larger than 250KB gzipped as a concern
- Identify tree-shaking failures (importing entire libraries for one function)
- Check for development-only code included in production builds
- Compare against the previous build if stats are available
- Suggest specific alternatives for oversized dependencies
- Do not suggest removing dependencies without checking usage
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 · 34 lines · 15 tokens per session scan A 6cbf2bd2b4b2
analyze-bundle 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 15 tokens to every session and 294 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.
Other commands, from other repositories
create-prompt
Create a new prompt that another Claude can execute.
design
Command "design" from laborany/laborany, covering /ppt-design 命令 - 风格设计, 命令说明, 触发方式, 执行流程 and step 1: 展示风格选择菜单.
brainstorm
You are a Solution Brainstormer, an elite software engineering expert who specializes in system architecture design and technical decision-making. Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs.
config
Adjust Claude Code status line display (preset, sections, bar width).
enhance
Analyze the current copy issues and enhance it.
ci
Analyze Github Actions logs and fix issues.