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 skills/igniteui/igniteui-cli/igniteui-react-optimize-bundle-sizenpx skills add IgniteUI/igniteui-cli --skill igniteui-react-optimize-bundle-sizegit clone --depth 1 https://github.com/IgniteUI/igniteui-cliWhat 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.00050 | $0.02928 |
| Opus 5 | $0.00025 | $0.01464 |
| Sonnet 5 | $0.00010 | $0.00586 |
| Haiku 4.5 | $0.00005 | $0.00293 |
Grade A, and why
igniteui-react-optimize-bundle-size 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 3d 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:
- igniteui-react-optimize-bundle-size — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 440 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Optimize Bundle Size
This skill helps users minimize their React application's bundle size when using Ignite UI for React by importing only the components they need, leveraging tree-shaking, and applying lazy loading strategies.
Example Usage
- "My bundle size is too large"
- "How do I reduce the size of igniteui-react?"
- "Import only the components I need"
- "Tree-shake unused components"
- "Optimize imports for production"
- "How do I lazy load the data grid?"
Related Skills
- igniteui-react-components — Choose only the components you need and set up your React project
- igniteui-react-customize-theme — Theming after optimization
When to Use
- Application bundle size is too large
- User wants to optimize for production
- User is importing more components than needed
- User asks about tree-shaking or optimization
- User wants to improve load times
- User wants to code-split heavy components like grids or charts
Key Principles
- Install only the packages you need — don't install
igniteui-react-gridsif you only use core UI components - Use named imports — enable tree-shaking by importing specific components
- Lazy load heavy components — use
React.lazy+Suspensefor grids, charts, and other large components - Analyze your bundle — use tools to identify what's being included
Granular Package Imports
Only install the packages you actually use:
| Package | Contains | Install only if you need… |
|---|---|---|
igniteui-react |
Buttons, inputs, dialogs, calendars, lists, etc. | Core UI components |
igniteui-react + igniteui-grid-lite |
Lightweight grid (IgrGridLite from igniteui-react/grid-lite) |
Simple tabular data (MIT, requires both packages) |
igniteui-react-grids |
DataGrid, TreeGrid, PivotGrid, HierarchicalGrid | Advanced data grids (commercial) |
igniteui-react-charts |
Category, Pie, Financial, Scatter charts | Charts and data visualization (commercial) |
igniteui-react-maps |
Geographic maps | Map visualizations (commercial) |
igniteui-react-gauges |
Radial and linear gauges | Gauge indicators (commercial) |
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.
- 3d ago First seen · 440 lines · 50 tokens per session scan A cd0be380fbcf
igniteui-react-optimize-bundle-size is a skill published in the GitHub repository IgniteUI/igniteui-cli (136 stars, last pushed 5d ago), licensed MIT. It adds 50 tokens to every session and 2,928 once invoked, about $0.0003 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 skills, from other repositories
logic-state-layer
Decision tree for whether logic belongs in the component class, a service, or an NgRx store, including service scope and where API calls go. Invoked by logic-placement and logic-review, not directly.
design
Use this skill to build user interfaces with Arena, a token-driven design system with React and Angular component libraries on a shared Tailwind layer, for production screens or for throwaway prototypes and mocks. Covers design tokens, colour, type, spacing, motion, iconography, and the accessibility pattern each…
vercel-ai-sdk-streaming
Build streaming AI features in Next.js with Vercel AI SDK, tool calling, RSC/UI hooks, and edge-safe API routes. Use for TypeScript fullstack AI UX with React Server Components.
react-nextjs-frontend
Apply frontend guidance for React and Next.js stacks, including routing, rendering strategy, state boundaries, and performance defaults. Use when a project uses React, Next.js, TypeScript, and component-driven UI delivery.
frontend-review
Frontend Code Review (Angular & React): Expert review of frontend code focusing on Angular, React, component architecture, state management, performance, accessibility, and UI patterns. Use whenever the user wants a review of frontend code, component design, state management, or mentions Angular, React, TypeScript…
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance…