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-version-update/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-version-update)<a href="https://agentmods.dev/skills/igniteui/igniteui-cli/igniteui-cli-template-version-update"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-cli/igniteui-cli-template-version-update/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-version-update"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-cli/igniteui-cli-template-version-update.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.00073 | $0.03531 |
| Opus 5.5 | $0.00029 | $0.01412 |
| Sonnet 5.5 | $0.00015 | $0.00706 |
| Haiku 4.5 | $0.00007 | $0.00353 |
Grade A, and why
igniteui-cli-template-version-update 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Template Version Update
Updates the Ignite UI package versions pinned in project and component templates: what ig new and ig add write into a user's package.json. The CLI's own dependencies and version are out of scope.
Input
- Scope: one or more of
angular,react,webcomponents, or specific package names. - Targets (optional): explicit versions, e.g.
igniteui-webcomponents 7.5.0. If none are given, the target for each package is its npmlatestdist-tag. - Mode:
update(default): Steps 1-7.dry-run: a read-only drift report. Run Steps 1-3, then stop and give the dry-run report (see Final Report). Edit no files and run no builds or smoke tests. Use it for "what is out of date?" questions;allis a valid scope here.
If the scope is missing, or a scope or target is ambiguous, stop and ask. In update mode the scope is always named explicitly; "everything" is never assumed.
Scope boundaries:
- A framework scope covers only that framework's root. With scope
webcomponents, theigniteui-webcomponentspins in Angular's wrapped-component templates (packages/igx-templates/.../chat,rating) are out of scope; report them as observations. - Packages shared by all frameworks' project templates (e.g.
@igniteui/material-icons-extended) are updated only when the user names them or the scope covers all three frameworks, so the frameworks don't diverge. Otherwise list them as observations.
Limits
Your changes are Ignite UI version strings, applied as patch or minor updates. Everything else is reported:
- Major updates (see Step 3) are stop items, never applied.
- Each pin keeps its range prefix (
~or^); report inconsistent prefixes as observations. - Pins stay where they are: hard-coded pins stay hard-coded unless the user asked to move them into constants.
- Non-Ignite UI dependencies in project templates (Angular, React, Vite, TypeScript, etc.) stay as they are. If a new Ignite UI version requires them to change, that is a stop item (Step 3).
- jQuery and Blazor templates are out of scope unless explicitly named.
CHANGELOG.mdis written at release time: propose a line in your report.
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.
- 9d ago First seen · 172 lines · 73 tokens per session scan A 4a24ca43c7cf
igniteui-cli-template-version-update is a skill published in the GitHub repository IgniteUI/igniteui-cli (137 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 3,531 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…
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…