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-mcp-tool/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-mcp-tool)<a href="https://agentmods.dev/skills/igniteui/igniteui-cli/igniteui-cli-mcp-tool"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-cli/igniteui-cli-mcp-tool/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-mcp-tool"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-cli/igniteui-cli-mcp-tool.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.00090 | $0.02938 |
| Opus 5.5 | $0.00036 | $0.01175 |
| Sonnet 5.5 | $0.00018 | $0.00588 |
| Haiku 4.5 | $0.00009 | $0.00294 |
Grade A, and why
igniteui-cli-mcp-tool 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Tool
Adds or changes a tool of the Ignite UI MCP server: packages/igniteui-mcp/igniteui-doc-mcp, published as @igniteui/mcp-server and started by ig mcp. Paths below are relative to that folder unless they start with packages/, spec/ or .agents/.
Input
- Change: a new tool, or the existing tool and what changes (a parameter, behavior, response text, description).
- For a new tool, also: the question it answers and the data behind it.
If the change, or for a new tool its question and data, is missing, stop and ask.
Limits
- Your changes are in
src/,spec/unit/mcp-runtime-spec.ts, the docs in Step 6 and, for a doc tool,../docs-backend/and../shared-fixtures/. A new non-TypeScript asset undersrc/tools/(likesetup_*.md) also needs its line inscripts/build.ts, the only thing that copies it intodist/;constants.tsreads those files at import, so a missing copy crashes the server at startup. - Tool and parameter names are a public contract. Tool names are written into the AI skills
ig ai-configcopies from the upstream library repos (scripts/update-skills.ts), andget_api_referencewith itsplatform/component/memberparameters is baked into the docs database asmcp:get_api_reference?…links. For a rename or removal, stop and report every reference you find (git grep -n <name>from the repository root). - The tool reads only data the package already ships: the
fileslist inpackage.jsonis off limits. When the tool needs a new data file, stop and report. - A new
DocsProvidermethod needs a new endpoint in the .NET backend. Confirm that scope with the user before starting. docs/*-api/is tracked build output. When API tools load 0 entries, stop and ask before runningnpm run build:docs:*.CHANGELOG.mdis written at release time: propose a line in your report.
Tool Anatomy
| Part | Where |
|---|---|
| Registration | src/index.ts: registerApiTools (backed by ApiDocLoader) or registerDocTools (backed by DocsProvider) |
| Input schema | src/tools/schemas.ts: an exported z.object and its z.infer type |
| Handler | src/tools/handlers.ts: create<Name>Handler(deps) returning (params) => Promise<CallToolResult> |
| Description | TOOL_DESCRIPTIONS.<tool_name> in src/tools/constants.ts |
| Usage guide | USAGE_GUIDE in src/tools/constants.ts, served as the igniteui-usage-guide prompt |
| Server instructions | instructions in src/index.ts: rules that span tools only (framework detection, library boundary, resolve_import before imports) |
| Deprecated components | src/config/deprecations.ts |
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 · 175 lines · 90 tokens per session scan A f86b372c914b
igniteui-cli-mcp-tool is a skill published in the GitHub repository IgniteUI/igniteui-cli (137 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 2,938 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…
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…