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-ai-config-skills-refresh/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-ai-config-skills-refresh)<a href="https://agentmods.dev/skills/igniteui/igniteui-cli/igniteui-cli-ai-config-skills-refresh"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-cli/igniteui-cli-ai-config-skills-refresh/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-ai-config-skills-refresh"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-cli/igniteui-cli-ai-config-skills-refresh.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.00124 | $0.01803 |
| Opus 5.5 | $0.00050 | $0.00721 |
| Sonnet 5.5 | $0.00025 | $0.00361 |
| Haiku 4.5 | $0.00012 | $0.00180 |
Grade A, and why
igniteui-cli-ai-config-skills-refresh 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI-Config Skills Refresh
Mirrors each framework repository's skills/ folder into the bundled skills of the ai-config project templates. ig ai-config copies these into a user's project when no installed Ignite UI package ships its own skills/ (resolveSkillsRoots in packages/core/util/ai-skills.ts).
| Framework | Source | Bundled copy |
|---|---|---|
| angular | IgniteUI/igniteui-angular |
packages/igx-templates/igx-ts/projects/ai-config/files/skills |
| react | IgniteUI/igniteui-react |
packages/cli/templates/react/igr-ts/projects/ai-config/files/skills |
| webcomponents | IgniteUI/igniteui-webcomponents |
packages/cli/templates/webcomponents/igc-ts/projects/ai-config/files/skills |
| blazor | IgniteUI/igniteui-blazor |
packages/cli/templates/blazor/igb/projects/ai-config/files/skills |
The release build (npm run build-pack, run by npm-publish.yml) re-copies the same folders from master through scripts/update-skills.ts, so the published package always ships master's skills. This workflow keeps the committed copies (used by local runs, specs and reviewers) in step with what ships, or pins them to another ref when asked.
Input
- Frameworks: one or more of
angular,react,webcomponents,blazor, orall. - Ref (optional): branch, tag or commit in the source repositories. Default
master, matching the release build. - Mode:
update(default): Steps 1-5.dry-run: Steps 1-2, then the dry-run report. No files change.
If the frameworks are missing, stop and ask. A ref other than master is a deliberate choice: repeat it in the report, because the next release build still copies from master.
Limits
- Your changes are the files under the bundled
skills/folders in the table, nothing else. Theai-configtemplates' other files (AGENTS.md, instruction files,index.ts) stay as they are. - The bundled copy is an exact mirror of the source
skills/folder. Content problems (broken links, bad frontmatter) are reported for the framework repository to fix, not edited here. - Do not run
scripts/update-skills.tsornpm run build:update-skills: theygit fetchandgit checkout -Binside the documentation submodules, which writes to git and moves submodule pointers. Use the script below, which reads from GitHub over HTTPS and runs no git commands.
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 · 114 lines · 124 tokens per session scan A c63626c19181
igniteui-cli-ai-config-skills-refresh is a skill published in the GitHub repository IgniteUI/igniteui-cli (137 stars, last pushed today), licensed MIT. It adds 124 tokens to every session and 1,803 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…
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…