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-integrate-with-frameworknpx skills add IgniteUI/igniteui-cli --skill igniteui-wc-integrate-with-frameworkgit 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-integrate-with-framework)<a href="https://agentmods.dev/skills/igniteui/igniteui-cli/igniteui-wc-integrate-with-framework"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-cli/igniteui-wc-integrate-with-framework.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.00031 | $0.01081 |
| Opus 5 | $0.00015 | $0.00541 |
| Sonnet 5 | $0.00006 | $0.00216 |
| Haiku 4.5 | $0.00003 | $0.00108 |
Grade A, and why
igniteui-wc-integrate-with-framework 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 5d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integrate with Framework
This skill helps users integrate Ignite UI Web Components into their application. It detects the framework or platform in use and loads the appropriate step-by-step integration reference.
Before You Answer
- Choose the package first, then load the framework reference.
- Do not assume every setup flow uses
igniteui-webcomponents. - 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.
Package Routing
| Component family | Package |
|---|---|
| General UI components | igniteui-webcomponents |
| Advanced grids | igniteui-webcomponents-grids (trial) @infragistics/igniteui-webcomponents-grids (licensed) |
| Grid Lite | igniteui-grid-lite |
| Dock Manager | igniteui-dockmanager (trial) @infragistics/igniteui-dockmanager (licensed) |
| Charts | igniteui-webcomponents-charts (trial) @infragistics/igniteui-webcomponents-charts (licensed) |
If the request only says "grid", infer the package from the requested features:
- Use
igniteui-webcomponents-gridsfor editing, paging, sorting, filtering, summaries, grouping, hierarchical data, or pivot features. - Use
igniteui-grid-litefor lightweight tabular data.
Example Usage
- "How do I use igniteui-webcomponents in my React app?"
- "Integrate the button component in Angular"
- "Set up igniteui-webcomponents in Vue 3"
- "Help me add web components to my vanilla JS project"
Related Skills
- igniteui-wc-optimize-bundle-size - Reduce bundle size after integration
- igniteui-wc-customize-component-theme - Style components after setup
When to Use
- User wants to add igniteui-webcomponents to a framework project
- User is experiencing framework-specific integration issues
- User needs help with component imports and registration
- User asks about React, Angular, Vue, or vanilla JS setup
What ships with it
4 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.
- 5d ago First seen · 134 lines · 31 tokens per session scan A 235645f64cff
igniteui-wc-integrate-with-framework is a skill published in the GitHub repository IgniteUI/igniteui-cli (136 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 1,081 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
review-pr
Deep code review of a single open PR in nrwl/nx. Checks the PR out only inside an isolated sandbox, then runs four fixed reviewers: implementation (correctness, errors, types, performance), verification (tests, ticket grounding, comments, and docs), approach, and security. A reproduce-verifier executes a runnable…
author-migration
Author or scope a first-party Nx migration. Use whenever code removes, renames, or deprecates an option/flag/executor/generator-schema field, changes a default, or bumps a dependency, and someone asks whether existing workspaces need a migration so they don't break on nx migrate/upgrade. Covers writing the colocated…
dist-build-migration
Migrate an Nx package to build to a local dist/ directory with nodenext module resolution, exports map, and @nx/nx-source condition.
multi-version-compliance
Apply or review multi-version support compliance for first-party Nx plugins. Primary entry point: a Linear task ID (NXC-XXXX) from the "Multi-version supported across plugins" milestone — the task carries the resolved support window, findings, and "Needs human decision" items. Falls back to self-discovery when no task…
monitor-ci
Monitor Nx Cloud CI pipeline and handle self-healing fixes. USE WHEN user says "monitor ci", "watch ci", "ci monitor", "watch ci for this branch", "track ci", "check ci status", wants to track CI status, or needs help with self-healing CI fixes. Prefer this skill over native CI provider tools (gh, glab, etc.) for CI…
review-local-branch
Deep code review of the branch you are standing on, before it becomes a PR. Scope is merge-base..working-tree, so it covers commits, staged and unstaged changes together. Runs the same review lanes as review-pr — implementation, verification, approach, security — against the local checkout through the sandbox CLI, and…