Borrowing it
Nothing to install: this file belongs to IgniteUI/igniteui-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/IgniteUI/igniteui-cli/master/.agents/skills/igniteui-cli-component-template/SKILL.mdgit 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-cli-component-template)<a href="https://agentmods.dev/skills/igniteui/igniteui-cli/igniteui-cli-component-template"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-cli/igniteui-cli-component-template/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-cli-component-template"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-cli/igniteui-cli-component-template.svg" alt="Reviewed on agentmods" width="80" 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.00081 | $0.01756 |
| Opus 5.5 | $0.00032 | $0.00702 |
| Sonnet 5.5 | $0.00016 | $0.00351 |
| Haiku 4.5 | $0.00008 | $0.00176 |
Grade A, and why
igniteui-cli-component-template 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 9d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Component Template
Adds the component templates users get with ig add <id> <name>, for Angular (igx-ts), React (igr-ts) and Web Components (igc-ts).
Read first: igniteui-cli-template-anatomy (layout, fields, placeholders, model templates).
Input
- Component: e.g. "Tile Manager", "Rating".
- Frameworks: one or more of
angular,react,webcomponents. - Variant (optional): defaults to a single
defaultvariant showing basic usage.
If either the component or the frameworks are missing, stop and ask.
Limits
Your changes are the new template folders and nothing else. Stop and report when the work needs more than that:
- Template base classes,
TemplateManager, project templates and other components' templates stay as they are. - Use an existing
groups.jsongroup. When none fits, stop and ask before adding or renaming one. - Use only package versions already pinned in the framework. When the component needs a package pinned nowhere in the framework, stop and report; version choice belongs to the
igniteui-cli-template-version-updateworkflow. - Every component, prop, event and import in the template is one you verified in Step 2.
- Angular, React and Web Components only; jQuery and Blazor are out of scope.
CHANGELOG.mdis written at release time: propose a line in your report.
Steps
1. Check What Already Exists
For every framework (not only those in scope), look for an existing template for this component:
- folder names and
this.idvalues under the three framework roots; - near-miss ids (
breadcrumb/breadcrumbs,nav-drawer/navigation-drawer,mask/mask-input).
Outcomes:
- Already exists in a target framework: stop and report; do not duplicate.
- Exists in another framework: reuse that exact id, group and naming.
- Exists in two other frameworks with different ids: stop and report the conflict; ask which id to use.
2. Verify the Component in the Pinned Version
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.
- 9d ago First seen · 117 lines · 81 tokens per session scan A 1e76a68a56fd
igniteui-cli-component-template is a skill published in the GitHub repository IgniteUI/igniteui-cli (137 stars, last pushed today), licensed MIT. It adds 81 tokens to every session and 1,756 once invoked, about $0.0003 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-10-21.
Other skills, from other repositories
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
authoring-benchmarks
Design, implement, run, debug, and interpret browser performance benchmarks for Elements components and utilities. Use whenever the user asks to benchmark or performance-test runtime code, create or update a .test.bench.ts file, compare benchmark results, investigate a browser performance regression, understand Vitest…
agent-starters
Verify every starter supported by the stable production NVIDIA Elements CLI from a fresh consumer environment, investigate failures, and prepare at most one focused repair pull request. Use for nightly or scheduled production starter verification and starter availability failures.
audit-ci
Run and analyze Elements cold CI performance profiles and propose evidence-backed build, test, lint, and dependency-graph improvements. Use whenever asked to profile or benchmark pnpm run ci, rerun ci:profile, create a CI performance audit, compare CI timings, find bottlenecks or the completion path, investigate a CI…
authoring-projects
Author a new standalone NVIDIA Elements workspace project containing a Lit component, including package files, the five test types, Wireit tasks, workspace and CI registration, metadata generation, documentation-site integration, dependency-lint configuration, and generated lock/notice files. Use when creating or…
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…