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-smoke-test/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-smoke-test)<a href="https://agentmods.dev/skills/igniteui/igniteui-cli/igniteui-cli-smoke-test"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-cli/igniteui-cli-smoke-test/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-smoke-test"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-cli/igniteui-cli-smoke-test.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.00115 | $0.03371 |
| Opus 5.5 | $0.00046 | $0.01348 |
| Sonnet 5.5 | $0.00023 | $0.00674 |
| Haiku 4.5 | $0.00012 | $0.00337 |
Grade A, and why
igniteui-cli-smoke-test 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ignite UI CLI: Build, Template Specs, Smoke Test
scripts/smoke-test.sh is the only check that a generated project actually installs and builds. Jasmine stubs PackageManager.installPackages, so a green Jasmine run says nothing about real npm resolution or TypeScript compilation of generated code. Run the build and the template specs first: they are fast and catch id and pin mistakes before a slow smoke run.
Build and Template Specs
- Dependencies are installed with yarn, scripts run with npm. Run
yarn installoryarn addonly when asked: either rewritesyarn.lock, which agents leave untouched. A build that fails on dependencies is reported, not "fixed" by reinstalling. npm run buildafter any.tschange. Jasmine and the smoke test run the compiled.js, so without a build they test stale code.npm run lintskipspackages/cli/templates/**and every**/files/**(ignored ineslint.config.mjs). React, Web Components and jQuery template code is therefore only linted inside a generated project (see "Checking a Kept Project").npm run jasmineignores arguments and always runs every spec. To run one file, pass the compiled spec to the Jasmine CLI:npx jasmine spec/templates/react-spec.js. Leavespec/jasmine-runner.tsas it is.- A run that reports INCOMPLETE only because some specs are pending (
xit/pending()) still exits 0 and counts as a pass. Any failed spec is a failure.
Specs That Guard Templates
| Spec | Guards |
|---|---|
spec/templates/angular-spec.ts |
Template ids exist; no file collisions between templates; every igniteui-angular pin in templates and project package.json equals IGNITEUI_ANGULAR_PACKAGE |
spec/templates/react-spec.ts |
Same, for all four IGNITEUI_REACT_* constants |
spec/templates/webcomponents-spec.ts |
Ids and collisions only. It does not check version pins against the constants |
spec/templates/template-contracts-spec.ts |
Every jQuery, React, Web Components and Blazor project and component template: matches its framework and project type, its template paths exist, it generates a config |
spec/unit/TemplateManager-spec.ts, spec/unit/list-spec.ts |
Template discovery and ig list output |
spec/acceptance/* |
ig new, ig add, ig generate end to end, with package install stubbed |
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 · 159 lines · 115 tokens per session scan A 0958ae1625d1
igniteui-cli-smoke-test is a skill published in the GitHub repository IgniteUI/igniteui-cli (137 stars, last pushed today), licensed MIT. It adds 115 tokens to every session and 3,371 once invoked, about $0.0005 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…