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/larouexnonprofitconsulting/larouex-fullstack-plugin/optimize-bundlegit clone --depth 1 https://github.com/LarouexNonprofitConsulting/larouex-fullstack-pluginWrote 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/larouexnonprofitconsulting/larouex-fullstack-plugin/optimize-bundle)<a href="https://agentmods.dev/commands/larouexnonprofitconsulting/larouex-fullstack-plugin/optimize-bundle"><img src="https://agentmods.dev/badge/commands/larouexnonprofitconsulting/larouex-fullstack-plugin/optimize-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.1 | $0.00000 | $0.00107 |
| Opus 5 | $0.00000 | $0.00053 |
| Sonnet 5 | $0.00000 | $0.00021 |
| Haiku 4.5 | $0.00000 | $0.00011 |
Grade A, and why
optimize-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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- optimize-bundle — 100% identical, 0 lines differ
What it actually says
Analyze and optimize JavaScript bundle size. Run @next/bundle-analyzer to visualize bundle composition. Implement code splitting with dynamic imports for large components. Add route-based code splitting for page components. Remove unused dependencies from package.json. Configure tree shaking in next.config.ts. Optimize third-party library imports (use specific imports instead of entire libraries). Replace heavy libraries with lighter alternatives. Implement lazy loading for non-critical components. Measure bundle size before and after optimizations. Provide detailed report with size reductions. Set bundle size budgets for future monitoring.
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.
- 2d ago First seen · 2 lines · 0 tokens per session scan A 83dc91de607c
optimize-bundle is a command published in the GitHub repository LarouexNonprofitConsulting/larouex-fullstack-plugin (8 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 107 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
add-error-boundary
Implement React error boundaries throughout the application. Create error boundary component with componentDidCatch lifecycle. Add fallback UI with friendly error message and retry button. Log errors to monitoring service (Sentry, Azure Monitor) with stack traces. Implement granular boundaries for different sections…
review-component
Review a specific React component file using code-review-agent and frontend-development-agent. Analyze component architecture, proper Server vs Client component usage, prop types, hooks patterns (useState, useEffect, useCallback, useMemo), accessibility attributes (ARIA labels, semantic HTML, keyboard navigation)…
scaffold-nextjs
Scaffold a basic Next.js 15 project with modern best practices.
migrate-to-nextjs15
Upgrade this Next.js project to version 15. Update package.json dependencies to Next.js 15 and React 19. Migrate App Router patterns and update metadata API usage following latest conventions. Fix breaking changes in configuration, middleware, and API routes. Update next.config.ts with new configuration options. Test…
deploy-azure-production
Deploy to Azure production with mandatory review gate and comprehensive validation.
deploy-railway-production
Deploy to Railway production environment with mandatory review gate and validation.