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-react/grid-lite-to-igr-grid-migrationnpx skills add IgniteUI/igniteui-react --skill grid-lite-to-igr-grid-migrationgit 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/grid-lite-to-igr-grid-migration)<a href="https://agentmods.dev/skills/igniteui/igniteui-react/grid-lite-to-igr-grid-migration"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-react/grid-lite-to-igr-grid-migration.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.00089 | $0.01943 |
| Opus 5 | $0.00044 | $0.00971 |
| Sonnet 5 | $0.00018 | $0.00389 |
| Haiku 4.5 | $0.00009 | $0.00194 |
Grade A, and why
grid-lite-to-igr-grid-migration 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.
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grid Lite → Premium Data Grid
Read the user's current Grid Lite usage first — columns, templates, data binding, dataPipelineConfiguration — then confirm APIs with get_doc({ framework: 'react', name: 'grid-editing' }) or get_api_reference({ platform: 'react', component: 'IgrGrid' }) rather than from memory. Grid APIs change between versions.
Is the migration warranted?
Grid Lite has none of these; each is a valid reason to move:
| Feature | IgrGrid |
|---|---|
| Cell / row editing | editable on the column, rowEditable on the grid |
| Batch editing with undo | transaction service |
| Row add / delete | rowEditable + IgrActionStrip |
| Row / cell / column selection | rowSelection, cellSelection, columnSelection |
| Paging | IgrPaginator child |
| Grouping | groupingExpressions |
| Summaries | hasSummary on the column |
| Column pinning / moving / hiding | pinned, moving, toolbar actions |
| Master-detail, hierarchical rows | row expansion, IgrTreeGrid, IgrHierarchicalGrid |
| Excel / CSV export | IgrGridToolbarExporter |
| Advanced filtering UI | filterMode="excelStyleFilter", IgrGridToolbarAdvancedFiltering |
| State persistence | IgrGridState |
| Row drag and drop | rowDraggable |
If none applies, staying on Grid Lite is lighter — see igniteui-react-optimize-bundle-size.
Setup
npm install --save igniteui-react-grids # or @infragistics/igniteui-react-grids when licensed
import { IgrGrid, IgrColumn } from 'igniteui-react-grids';
import 'igniteui-react-grids/grids/themes/light/bootstrap.css'; // in addition to the base theme
No registration. IgrGridModule.register() is deprecated and unnecessary — the React wrapper registers the element on import. Do not add it, and delete it if present.
Minimal port
import { useRef, useState } from 'react';
import { IgrGrid, IgrColumn } from 'igniteui-react-grids';
import 'igniteui-react-grids/grids/themes/light/bootstrap.css';
export default function Products({ data }: { data: Product[] }) {
const grid = useRef<IgrGrid>(null);
return (
<IgrGrid ref={grid} data={data} primaryKey="id" autoGenerate={false}
height="600px" allowFiltering={true}>
<IgrColumn field="name" header="Name" sortable filterable resizable />
<IgrColumn field="price" header="Price" dataType="number" sortable />
</IgrGrid>
);
}
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 Changed · -93 lines · +28 tokens per session 3dae3e9c55cc
- 6d ago First seen · 275 lines · 61 tokens per session scan A 376b6b20fada
grid-lite-to-igr-grid-migration is a skill published in the GitHub repository IgniteUI/igniteui-react (56 stars, last pushed 4d ago), licensed MIT. It adds 89 tokens to every session and 1,943 once invoked, about $0.0004 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
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…
nextjs-app-router
Full end-to-end tRPC setup for Next.js App Router. Covers route handler with fetchRequestHandler (GET + POST exports), TRPCProvider with QueryClientProvider, createTRPCOptionsProxy for RSC prefetching, HydrateClient/HydrationBoundary for hydration, useSuspenseQuery for Suspense, and server-side callers.
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…
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
nextjs-pages-router
Set up tRPC in Next.js Pages Router with createNextApiHandler, createTRPCNext, withTRPC HOC, SSR via ssr option and ssrPrepass, SSG via createServerSideHelpers with getStaticProps, and server-side helpers for getServerSideProps prefetching.
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.