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/Ashikparvez89/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/ashikparvez89/larouex-fullstack-plugin/optimize-bundle)<a href="https://agentmods.dev/commands/ashikparvez89/larouex-fullstack-plugin/optimize-bundle"><img src="https://agentmods.dev/badge/commands/ashikparvez89/larouex-fullstack-plugin/optimize-bundle/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/ashikparvez89/larouex-fullstack-plugin/optimize-bundle"><img src="https://agentmods.dev/badge/commands/ashikparvez89/larouex-fullstack-plugin/optimize-bundle.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.00107 |
| Opus 5.5 | $0.00000 | $0.00043 |
| Sonnet 5.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 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.
This is a copy
100% identical to optimize-bundle — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 1mo ago First seen · 2 lines · 0 tokens per session scan A 83dc91de607c
optimize-bundle is a command published in the GitHub repository Ashikparvez89/larouex-fullstack-plugin (3 stars, last pushed 8d 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. It is 100% identical to optimize-bundle, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
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.
add-auth
Implement authentication system with comprehensive user management.
audit-accessibility
Audit the project for WCAG 2.1 AA accessibility compliance.
audit-security
Perform comprehensive security audit of the current project.
review-before-deploy
Execute comprehensive pre-deployment review using code-review-agent with all relevant platform agents. Run complete deployment readiness checklist: verify all tests pass (unit, integration, E2E), security audit clean (no Critical/High issues), performance benchmarks met (Lighthouse > 90), TypeScript compilation…