Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/igniteui/igniteui-cli/igniteui-blazor-themingnpx skills add IgniteUI/igniteui-cli --skill igniteui-blazor-theminggit 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-blazor-theming)<a href="https://agentmods.dev/skills/igniteui/igniteui-cli/igniteui-blazor-theming"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-cli/igniteui-blazor-theming.svg" alt="Measured on agentmods" 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 | $0.00157 | $0.03166 |
| Opus 5 | $0.00078 | $0.01583 |
| Sonnet 5 | $0.00031 | $0.00633 |
| Haiku 4.5 | $0.00016 | $0.00317 |
Grade A, and why
igniteui-blazor-theming 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 4d 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ignite UI for Blazor - Theming and Styling
Description
This skill teaches AI agents how to theme Ignite UI for Blazor applications using built-in CSS theme files, CSS custom properties, CSS shadow parts, and the Ignite UI Theming MCP server. It covers theme switching, palette generation, component-level design tokens, global layout tokens, and scoped CSS customization.
Prerequisites
- A Blazor project using Ignite UI for Blazor components
- A theme CSS file linked in the host page (see
references/common-patterns.md) - The Ignite UI Theming MCP server (
igniteui-theming) available as a tool provider
AGENT INSTRUCTION - MCP Server Setup (REQUIRED)
Before using any theming tools, you MUST verify the MCP server is available by calling any lightweight theming MCP tool. This skill is already scoped to Ignite UI for Blazor, so use
platform: "blazor"in theming tool calls. If the theming tool is not available or the call fails, you MUST automatically configure it by following the setup process steps described below.After writing the file, inform the user that the MCP server has been configured and they may need to reload the editor for the tools to activate. Start the MCP server and wait for that MCP server to start before continuing the theming related work. Do NOT skip this step or ask the user to do it manually.
Setting Up the Theming MCP Server
Full setup instructions for VS Code, Cursor, Claude Desktop, and JetBrains IDEs are in
references/mcp-setup.md. Read that file for editor-specific configuration steps and verification.
Theming Architecture
| Layer | Purpose |
|---|---|
| Built-in theme CSS | Baseline Bootstrap, Material, Fluent, or Indigo styling in light/dark variants |
| Palette tokens | Global color CSS variables used across components |
| Component design tokens | Component-scoped CSS custom properties generated or discovered with MCP |
| CSS shadow parts | Fine-grained internal element styling only when the component doc lists supported parts |
| Layout tokens | Global roundness, spacing, and size controls generated by MCP tools |
What ships with it
2 files 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.
- 4d ago First seen · 260 lines · 157 tokens per session scan A d9ce7c93dec9
igniteui-blazor-theming is a skill published in the GitHub repository IgniteUI/igniteui-cli (136 stars, last pushed today), licensed MIT. It adds 157 tokens to every session and 3,166 once invoked, about $0.0008 per session on Opus 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-08-30.
Other skills, from other repositories
review-pr
Deep code review of a single open PR in nrwl/nx. Checks the PR out only inside an isolated sandbox, then runs four fixed reviewers: implementation (correctness, errors, types, performance), verification (tests, ticket grounding, comments, and docs), approach, and security. A reproduce-verifier executes a runnable…
author-migration
Author or scope a first-party Nx migration. Use whenever code removes, renames, or deprecates an option/flag/executor/generator-schema field, changes a default, or bumps a dependency, and someone asks whether existing workspaces need a migration so they don't break on nx migrate/upgrade. Covers writing the colocated…
dist-build-migration
Migrate an Nx package to build to a local dist/ directory with nodenext module resolution, exports map, and @nx/nx-source condition.
multi-version-compliance
Apply or review multi-version support compliance for first-party Nx plugins. Primary entry point: a Linear task ID (NXC-XXXX) from the "Multi-version supported across plugins" milestone — the task carries the resolved support window, findings, and "Needs human decision" items. Falls back to self-discovery when no task…
monitor-ci
Monitor Nx Cloud CI pipeline and handle self-healing fixes. USE WHEN user says "monitor ci", "watch ci", "ci monitor", "watch ci for this branch", "track ci", "check ci status", wants to track CI status, or needs help with self-healing CI fixes. Prefer this skill over native CI provider tools (gh, glab, etc.) for CI…
review-local-branch
Deep code review of the branch you are standing on, before it becomes a PR. Scope is merge-base..working-tree, so it covers commits, staged and unstaged changes together. Runs the same review lanes as review-pr — implementation, verification, approach, security — against the local checkout through the sandbox CLI, and…