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-changelog/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-changelog)<a href="https://agentmods.dev/skills/igniteui/igniteui-cli/igniteui-cli-changelog"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-cli/igniteui-cli-changelog/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-changelog"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-cli/igniteui-cli-changelog.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.00065 | $0.01382 |
| Opus 5.5 | $0.00026 | $0.00553 |
| Sonnet 5.5 | $0.00013 | $0.00276 |
| Haiku 4.5 | $0.00006 | $0.00138 |
Grade A, and why
igniteui-cli-changelog 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog
Release notes for Ignite UI CLI live in CHANGELOG.md. A section is written when a release is cut (commits like chore(*): cut 15.8.1), summarizing the PRs merged since the previous cut.
Input
- Version and date of the release (e.g.
15.9.0,2026-10-15). If missing, stop and ask. - Mode:
draft(default): output the section text only; the working tree stays unchanged.write: insert the section at the top ofCHANGELOG.md.
- Optional range: a commit range to use instead of "since the last cut".
Limits
- Your one change is the new section at the top of
CHANGELOG.md, inwritemode only. Existing release sections stay as they are. - Versioning and publishing belong to the release process:
npm run releaseandnpm run versionare never run. - Every bullet describes something visible in the commits and their diffs.
Steps
1. Find the Range
The previous release is the most recent commit whose subject matches cut <version> (e.g. git log --format='%h %s' | grep -E 'cut [0-9]+\.[0-9]+'). Not every commit touching CHANGELOG.md is a cut. Range = that commit (exclusive) to HEAD, unless the user gave one.
2. Collect Changes
git log --format='%h %s' <range>. Subjects end with (#<PR>). For each PR-level commit:
- read the diff summary (
git show --stat <hash>) and, where the subject is vague, the relevant diff; - if the
ghCLI is available and authenticated,gh pr view <PR>for the description. Descriptions are often the empty PR template; then rely on the diff.
3. Select and Group
Classify each commit by its effect on users, not only by its prefix:
| Commit | Treatment |
|---|---|
| Release cut, merge commit | Skip |
Only touches CHANGELOG.md (e.g. rewording an older section) |
Skip |
| Dependency bump of repository tooling (dev deps, lockfile, MCP server deps) | Fold into one build(deps) bullet listing notable packages and all PR links |
Dependency or version change that alters what scaffolded projects get (template package.json, constants.ts, template packages) |
Its own bullet as chore(<framework>), even if the commit says build(deps) |
| No conventional prefix | Infer type and scope from the diff; mention the inference under "Needs human input" |
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 · 100 lines · 65 tokens per session scan A 2d2f319a40f5
igniteui-cli-changelog is a skill published in the GitHub repository IgniteUI/igniteui-cli (137 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 1,382 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-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…
summarize-releases
Create a monthly NVIDIA Elements “What’s New” docs page, matching video, and concise, copy-ready summary from local release tags, tagged changelogs, package versions, and commit history. Use for a scheduled release PR, monthly update, release roundup, changelog digest, Slack blurb, announcement, or plain-language…
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.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
skillshare-changelog
Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…