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-cli --skill igniteui-blazor-generate-from-image-designgit clone --depth 1 https://github.com/IgniteUI/igniteui-cliWrote 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-cli/igniteui-blazor-generate-from-image-design)<a href="https://agentmods.dev/skills/igniteui/igniteui-cli/igniteui-blazor-generate-from-image-design"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-cli/igniteui-blazor-generate-from-image-design/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-cli/igniteui-blazor-generate-from-image-design"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-cli/igniteui-blazor-generate-from-image-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00127 | $0.04427 |
| Opus 5.5 | $0.00051 | $0.01771 |
| Sonnet 5.5 | $0.00025 | $0.00885 |
| Haiku 4.5 | $0.00013 | $0.00443 |
Grade A, and why
igniteui-blazor-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 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.
How it starts
The opening of the file, as written. The whole thing — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementing Ignite UI Blazor Views from Design Images
MANDATORY AGENT PROTOCOL
Before writing any implementation code, you must complete these steps in order:
- Analyze the image and identify all visible regions and UI patterns.
- Read references/component-mapping.md.
- This skill is Blazor-only. Check NuGet package (
IgniteUI.Blazor.Lite,IgniteUI.Blazor.GridLitefor general purpose components and light-weight grid, orIgniteUI.Blazor/IgniteUI.Blazor.Trialfor specialized feature-rich grids and charts) only when theming or component availability depends on it. - To apply a theme, use the theming workflow from this skill and the dedicated
igniteui-blazor-themingskill; use theigniteui-themingMCP tools instead of styling from memory. - Call
get_docfor every chosen component family before using it. - Read references/gotchas.md now — after docs, before writing any code. Read the file in full. Some entries are component-specific; others apply broadly to any chart, any themed component, or any scoped CSS. Apply every entry that is relevant to what you are building. This is a blocking step: do not start implementation until you have read the whole file and checked it against your component list.
- Only then start coding.
Workflow
- Analyze the design image - Read the image, identify every UI section, component, layout structure.
- Confirm NuGet package if needed - this skill is Blazor-only; use
IgniteUI.Blazor.Lite,IgniteUI.Blazor.GridLitefor general purpose components and the light-weight grid, andIgniteUI.Blazor(trial version available publicly asIgniteUI.Blazor.Trial) for specialized feature-rich grids and charts. - Discover components - Call
list_componentswith targeted filters andframework: "blazor"to find matching components for each UI pattern. - Look up component docs - Call
get_docfor every chosen component family before coding. - Generate theme - (a) Extract colors and call
create_paletteorcreate_custom_palettewithplatform: "blazor"andoutput: "css"— do not usecreate_themefor Blazor, it produces Sass requiring compilation. Optionally callcreate_elevationsandcreate_typographyfor elevation and font overrides. (b) After a palette exists, prefer using design tokens or scoped semantic CSS variables over raw literals. (c) For every Ignite UI component, callget_component_design_tokens, map extracted image tokens to token roles, then callcreate_component_themewith the tokens differing from the global theme for the specific component. - Implement - Build the screenshot-first layout, data, and view components.
- Refine - Use the
set_size,set_spacing,set_roundnesstools to refine the view's visual fidelity against the image, then iterate on implementation and theming until the view matches the design closely. - Validate - Build, test, run, compare against the image, and fix differences.
What ships with it
2 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.
- 1mo ago First seen · 285 lines · 127 tokens per session scan A d60678a1b801
igniteui-blazor-generate-from-image-design is a skill published in the GitHub repository IgniteUI/igniteui-cli (137 stars, last pushed today), licensed MIT. It adds 127 tokens to every session and 4,427 once invoked, about $0.0005 per session on Opus 5.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
authoring-patterns
Convert validated playground templates or HTML compositions into reusable pattern files (.examples.ts) in the pattern library. Use this skill whenever the user wants to save, persist, store, or catalog a template, prototype, composition, or playground result as a reusable pattern. Trigger on phrases like "save as…
elements
Use this skill by default for any UI-related work or with NVIDIA Elements (nve-), including creating, editing, reviewing, or debugging HTML, CSS, layout, theming, components, applications, prototypes, Claude Artifacts, Codex Sites pages, and standalone UI artifacts.
audit-accessibility
Unified accessibility auditing workflow across static analysis, runtime testing, ARIA patterns, keyboard navigation, and color contrast. Use this skill whenever the user mentions accessibility, a11y, WCAG, ARIA roles, axe tests, screen readers, focus management, keyboard navigation, color contrast, or wants to audit…
authoring-tests
Write and run automated tests for Elements components including unit, accessibility, visual, SSR, and lighthouse tests. Use this skill whenever the user wants to write, create, update, or debug test files (.test.ts, .test.axe.ts, .test.visual.ts, .test.ssr.ts, .test.lighthouse.ts). Also trigger when the user asks…
skillshare-ui-website-style
Skillshare frontend design system for the React dashboard (ui/) and Docusaurus website (website/). Use this skill whenever you: build or modify a dashboard page or component in ui/src/, style or layout website pages or custom CSS in website/, create new React components for the dashboard, add pages to the dashboard…
antd
Use when the user's task involves Ant Design (antd) — writing antd components, debugging antd issues, querying antd APIs/props/tokens/demos, migrating between antd versions, or analyzing antd usage in a project. Triggers on antd-related code, imports from 'antd', or explicit antd questions.