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-template-anatomy/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-template-anatomy)<a href="https://agentmods.dev/skills/igniteui/igniteui-cli/igniteui-cli-template-anatomy"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-cli/igniteui-cli-template-anatomy/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-template-anatomy"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-cli/igniteui-cli-template-anatomy.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.00097 | $0.02698 |
| Opus 5.5 | $0.00039 | $0.01079 |
| Sonnet 5.5 | $0.00019 | $0.00540 |
| Haiku 4.5 | $0.00010 | $0.00270 |
Grade A, and why
igniteui-cli-template-anatomy 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ignite UI CLI: Template Anatomy
Discovery
Templates are discovered by scanning folders. There is no registry file. A component appears in ig add / ig list when its folder contains a component index.ts and at least one variant folder with its own index.ts. groups.json only holds group descriptions; it changes only when a new group is introduced.
Framework Roots
| Framework | Project type | Root | Template base class | Constants |
|---|---|---|---|---|
| Angular | igx-ts |
packages/igx-templates/igx-ts/ |
packages/igx-templates/IgniteUIForAngularTemplate.ts |
packages/igx-templates/constants.ts |
| React | igr-ts |
packages/cli/templates/react/igr-ts/ |
packages/cli/lib/templates/IgniteUIForReactTemplate.ts |
packages/cli/templates/react/igr-ts/constants.ts |
| Web Components | igc-ts |
packages/cli/templates/webcomponents/igc-ts/ |
packages/cli/lib/templates/IgniteUIForWebComponentsTemplate.ts |
packages/cli/templates/webcomponents/igc-ts/constants.ts |
jQuery (packages/cli/templates/jquery/js/) is legacy and Blazor (packages/cli/templates/blazor/igb/) has no component templates. Both are out of scope for the template workflows unless the user asks.
@igniteui/angular-templates is a separate npm package: Angular templates import only from packages/igx-templates/ and @igniteui/cli-core, never from packages/cli/templates/. A version Angular shares with Web Components (e.g. igniteui-webcomponents for wrapped components) is kept on the Angular side.
Component Template Layout
<root>/<component-id>/
index.ts ← component: BaseComponent from @igniteui/cli-core
<variant>/ ← usually "default"; grids use e.g. "basic", "grid-editing"
index.ts ← template: extends the framework's template base class
files/src/app/__path__/ ← files copied into the generated project
__filePrefix__.<ext>
Component index.ts (same shape in all three frameworks):
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 · 155 lines · 97 tokens per session scan A 637a8dce9f04
igniteui-cli-template-anatomy is a skill published in the GitHub repository IgniteUI/igniteui-cli (137 stars, last pushed today), licensed MIT. It adds 97 tokens to every session and 2,698 once invoked, about $0.0004 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…
agent-dependencies
Perform one conservative dependency or toolchain upgrade in the Elements monorepo and open a validated pull request. Use for nightly or unattended dependency maintenance, outdated package checks, first-party actions/ GitHub Actions updates, and pinned mise tool updates. Use the github-dependabot skill instead when the…
summarize-video-releases
Create the 24–36 second marketing video for a monthly NVIDIA Elements “What’s New” post, rendered to projects/site/public/static/video/releases/MM-YYYY.webm from real Elements components, with feature snapshots inserted into the post. Use after the summarize-releases skill creates or updates a post, and whenever…
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-debug-ci
Investigate failed scheduled or nightly GitHub Actions runs on the default branch, determine whether the failure is reproducible and repository-owned, implement the smallest evidence-backed fix, validate it, and open a pull request. Use when a failed nightly CI event starts an agent, or when the standard CI or…
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…