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/igniteui-react-generate-from-image-designnpx skills add IgniteUI/igniteui-react --skill igniteui-react-generate-from-image-designgit 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-generate-from-image-design)<a href="https://agentmods.dev/skills/igniteui/igniteui-react/igniteui-react-generate-from-image-design"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-react/igniteui-react-generate-from-image-design.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 | $0.00075 | $0.01735 |
| Opus 5 | $0.00037 | $0.00868 |
| Sonnet 5 | $0.00015 | $0.00347 |
| Haiku 4.5 | $0.00007 | $0.00173 |
Grade A, and why
igniteui-react-generate-from-image-design 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 today.
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
98% identical to igniteui-react-generate-from-image-design — 4 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementing a React View from a Design Image
React only — pass platform: 'react' / framework: 'react' to every MCP call.
Order of work
- Read the image. Identify every region, its component, and the layout structure.
- Inspect the app. Existing theme imports, design system, palette overrides, installed packages.
- Look up the components you chose before writing them —
get_doc,get_api_reference. - Theme — global layer only if the app has none, then per-component tokens.
- Implement the layout, mock data, and view.
- Validate — build, run, compare with the image, iterate.
Steps 3 and 4 use MCP servers where available; both are optional. Without them, read the installed .d.ts files (node_modules/igniteui-webcomponents/components/<name>/) for props, @slot, @csspart, and @cssproperty names, and theme with the palette shades documented in igniteui-react-customize-theme.
1. Read the image
Record, per region: layout role and proportions, component type, colors, type scale, borders/radius/shadow, data shape, and spacing rhythm.
Resolve layout as CSS Grid rows and columns that preserve the observed proportions — do not reverse-engineer exact pixel values or invent breakpoints yet. Get desktop proportions right first, then add stacking rules.
Before coding, state briefly: chosen component per region, any region falling back to plain HTML and why, theme strategy, packages needed, and assumptions you made where the image is ambiguous.
Start every region from an Ignite UI component. Fall back to semantic HTML only when the component's DOM structure stays incompatible after CSS overrides and ::part() are considered, and say so in a comment. Component picks live in COMPONENTS.md; use list_components({ framework: 'react', filter: '<narrow term>' }) to discover more. Narrow filters work better — 'list view', not 'list'.
What ships with it
1 file 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.
- today Changed · -129 lines · -62 tokens per session 9cb93ca7ff6c
- 4d ago First seen · 230 lines · 137 tokens per session scan A 51f85bb3297d
igniteui-react-generate-from-image-design is a skill published in the GitHub repository IgniteUI/igniteui-react (56 stars, last pushed 2d ago), licensed MIT. It adds 75 tokens to every session and 1,735 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to igniteui-react-generate-from-image-design, differing in 4 lines, and is treated as a copy.
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…
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…
material-ui-review
Review the current diff for regressions, correctness bugs, tests, simplifications, and docs issues, scaling depth to a low/medium/high/xhigh/max effort level. Use ONLY when explicitly requested by name: the user runs /material-ui-review, writes $material-ui-review, or asks for "the Material UI review skill". Do NOT…
row-selection
Maintain rowSelection ID state with stable getRowId, single, multi, subrow, and Shift-range rules, selected row models, handler anchors, and manual-pagination semantics. Load when implementing getToggleSelectedHandler, enableRowRangeSelection, selectChildren, deselectParents, or selected IDs that outlive loaded Row…
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.
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.