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 skills add IgniteUI/igniteui-react --skill igniteui-react-componentsgit clone --depth 1 https://github.com/IgniteUI/igniteui-reactWrote 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/skills/igniteui/igniteui-react/igniteui-react-components)<a href="https://agentmods.dev/skills/igniteui/igniteui-react/igniteui-react-components"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-react/igniteui-react-components/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/skills/igniteui/igniteui-react/igniteui-react-components"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-react/igniteui-react-components.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.00200 | $0.01199 |
| Opus 5.5 | $0.00080 | $0.00480 |
| Sonnet 5.5 | $0.00040 | $0.00240 |
| Haiku 4.5 | $0.00020 | $0.00120 |
Grade A, and why
igniteui-react-components 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 19d 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
92% identical to igniteui-react-components — 193 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ignite UI for React Components
Igr* components are React wrappers around igc-* web components. Everything below follows from that.
Non-negotiables
- Import a theme CSS file or components render unstyled with broken icons.
- No
.register()forigniteui-react,igniteui-react-grids,igniteui-react/grid-lite, origniteui-react-dockmanager— the wrapper registers the element on import. Charts, gauges, and maps (separate legacy packages) do require.register(). - CSS selectors must target
igc-*, neverIgrButton. Use::part()for shadow DOM internals. - Events are
CustomEvent, not ReactSyntheticEvent. Reade.detail. - Never set column
widthonIgrColumn/IgrGridLiteColumnunless asked — see DATAVIZ.md. - Charts, gauges, maps, and grids need an explicitly sized container or they render at zero height.
Packages
| Need | Install | Import from |
|---|---|---|
| Core UI (MIT) | igniteui-react |
igniteui-react |
| Grid Lite (MIT) | igniteui-react + igniteui-grid-lite |
igniteui-react/grid-lite |
| Data/Tree/Pivot/Hierarchical Grid | igniteui-react-grids |
igniteui-react-grids |
| Dock Manager | igniteui-react-dockmanager |
igniteui-react-dockmanager |
| Charts, gauges, maps | igniteui-react-charts / -gauges / -maps |
same |
Commercial packages also publish under @infragistics/… for licensed workspaces; use that scope and its matching CSS path when the workspace already uses it. igniteui-grid-lite is an optional peer of igniteui-react — Grid Lite needs both installed.
Quick start
npm install igniteui-react
// main.tsx — theme first, your overrides after
import 'igniteui-webcomponents/themes/light/bootstrap.css';
import { IgrButton, IgrInput } from 'igniteui-react';
<IgrInput label="Name" />
<IgrButton>Submit</IgrButton>
Themes: igniteui-webcomponents/themes/{light|dark}/{bootstrap|material|fluent|indigo}.css.
Grids need a second import: igniteui-react-grids/grids/themes/{light|dark}/<design-system>.css.
Next.js has no single entry point — import the theme CSS in app/layout.tsx or in each 'use client' file that uses components.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 19d ago Changed · +1 lines · +110 tokens per session 58085328cca5
- 1mo ago Changed · -109 lines · +18 tokens per session 93c3e37ac346
- 1mo ago First seen · 182 lines · 72 tokens per session scan A 1cf162413f78
igniteui-react-components is a skill published in the GitHub repository IgniteUI/igniteui-react (56 stars, last pushed 4d ago), licensed MIT. It adds 200 tokens to every session and 1,199 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to igniteui-react-components, differing in 193 lines, and is treated as a copy.
Other skills, from other repositories
material-ui-nextjs
Integrates Material UI with Next.js App and Pages routers using @mui/material-nextjs, Emotion cache providers, next/font, CSS layers with Tailwind/CSS Modules, Link component prop patterns, CSS theme variables SSR notes, and App Router useSearchParams + Suspense. Use when setting up or debugging MUI in a Next.js app.
debugging-wizard
Parses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven methodology to isolate and resolve bugs. Use when investigating errors, analyzing stack traces, finding root causes of unexpected behavior, troubleshooting…
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
chakra-ui-refactor
Review, convert, and improve UI code using Chakra UI v3. Use this skill whenever a user wants to review Chakra UI code for issues, convert plain HTML/CSS, Tailwind, CSS Modules, or styled-components to Chakra UI, clean up messy Chakra components, fix layout structure or token usage, or asks anything like "is this…
devtools-react
React adapter for the json-render devtools inspector. Use whenever the user wants to add, configure, or troubleshoot @json-render/devtools-react in a React json-render app, including spec inspection, state editing, action and stream timelines, catalog browsing, or DOM picking.
material-ui-styling
Chooses the right Material UI styling approach (sx, styled, theme overrides, global CSS) from official MUI guidance. Use when styling @mui/material components, customizing themes, overriding slots, or comparing sx vs styled.