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-wc-choose-componentsnpx skills add IgniteUI/igniteui-cli --skill igniteui-wc-choose-componentsgit 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-wc-choose-components)<a href="https://agentmods.dev/skills/igniteui/igniteui-cli/igniteui-wc-choose-components"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-cli/igniteui-wc-choose-components.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.00034 | $0.07674 |
| Opus 5 | $0.00017 | $0.03837 |
| Sonnet 5 | $0.00007 | $0.01535 |
| Haiku 4.5 | $0.00003 | $0.00767 |
Grade A, and why
igniteui-wc-choose-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 6d 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 — 432 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Choose the Right Ignite UI Components
This skill helps AI agents and developers identify the best Ignite UI components for any UI requirement, then provides direct links to official documentation, usage examples, and API references.
Prerequisites
- The Ignite UI CLI MCP server (
igniteui-cli) available as a tool provider
AGENT INSTRUCTION — MCP Server Setup (REQUIRED)
Before using the Ignite UI CLI MCP tools, you MUST verify the MCP server is available by calling
list_components. If the tool is not available or the call fails, you MUST automatically configure it by following the setup instructions inreference/mcp-setup.md.After writing the file, inform the user that the MCP server has been configured and they may need to reload the editor for the tools to activate. Start the MCP server and wait for that MCP server to start before continuing the component-related work. Do NOT skip this step or ask the user to do it manually.
Setting Up the Ignite UI CLI MCP Server
Full setup instructions for VS Code, Cursor, Claude Desktop, and JetBrains IDEs are in
reference/mcp-setup.md. Read that file for editor-specific configuration steps and verification.
Before You Answer
- Choose the package before writing imports or install steps.
- If the required package is not present in
package.json, add or install the correct Ignite UI dependency first. Absence frompackage.jsondoes not mean the package is invalid. - If the user also needs setup or code, then load igniteui-wc-integrate-with-framework.
Example Usage
- "What component should I use to display a list of items with actions?"
- "I need a date picker for a booking form"
- "How do I show file upload progress?"
- "What's the best component for a navigation sidebar?"
- "I need a searchable dropdown with multi-select"
- "Build a dashboard layout with cards and a data grid"
- "I want to display hierarchical/tree data"
- "Show me components for notifications and alerts"
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.
- 6d ago First seen · 432 lines · 34 tokens per session scan A 50f5322ed6ff
igniteui-wc-choose-components is a skill published in the GitHub repository IgniteUI/igniteui-cli (136 stars, last pushed 2d ago), licensed MIT. It adds 34 tokens to every session and 7,674 once invoked, about $0.0002 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
nextjs-fullstack
Use for Next.js App Router, React Server Components, server actions, API routes, auth, database integration, caching, deployment, or full-stack product features.
react-component-design
Designs or reviews React component APIs. Handles prop drilling decisions, composition patterns, controlled/uncontrolled contracts, and minimal public API surfaces for React 18+ TypeScript components. Invoked when creating new components, refactoring existing ones, or reviewing component contracts.
cometchat-nextjs-patterns
Framework-specific patterns for integrating CometChat React UI Kit v6 into Next.js projects (App Router and Pages Router). Covers SSR prevention, provider setup, route placement, API routes, and common pitfalls.
cometchat-react-patterns
Framework-specific patterns for integrating CometChat React UI Kit v6 into React projects (Vite or CRA). Covers provider setup, routing, layout integration, env vars, and common pitfalls.
cometchat-react-push
Push notifications for CometChat React UI Kit v6 in Vite / Next.js / React Router / Astro projects. Recommended path is CometChat-native web push via Firebase Cloud Messaging for Web — CometChatNotifications.registerPushToken(token, PushPlatforms.FCMWEB) + a dashboard FCM provider, so CometChat's own backend delivers…
nextjs-server-components
Use when deciding Server vs Client Component boundaries in Next.js 16, fetching data directly in components, or streaming with Suspense.