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 skills add IgniteUI/igniteui-react --skill skill-authoringgit clone --depth 1 https://github.com/IgniteUI/igniteui-reactWrote 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-react/skill-authoring)<a href="https://agentmods.dev/skills/igniteui/igniteui-react/skill-authoring"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-react/skill-authoring/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-react/skill-authoring"><img src="https://agentmods.dev/badge/skills/igniteui/igniteui-react/skill-authoring.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.00163 | $0.00887 |
| Opus 5.5 | $0.00065 | $0.00355 |
| Sonnet 5.5 | $0.00033 | $0.00177 |
| Haiku 4.5 | $0.00016 | $0.00089 |
Grade A, and why
skill-authoring 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 17d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ignite UI for React — Skill Authoring
Quick-reference for writing a SKILL.md that agents can discover and load reliably.
Location
- Internal, contributor-facing skills:
.agents/skills/<name>/SKILL.md - Public skills that ship with the
igniteui-reactpackage:skills/<name>/SKILL.md - The folder name must match the
namefield.
Frontmatter
| Field | Rules |
|---|---|
license |
Required. Must specify the license under which the skill is released. Default is MIT. |
name |
Required. Max 64 characters. Lowercase letters, numbers, and hyphens only. No XML tags. No reserved words (anthropic, claude). Public skills use the igniteui-react- prefix; internal skills use a plain kebab-case name. |
description |
Required. Non-empty. Max 1,024 characters. No XML tags. |
Write the description in the third person: say what the skill covers, then add both markers:
WHEN TO USE:the tasks or triggers that should load the skill.WHEN NOT TO USE:nearby tasks it does not cover, naming the skill to use instead.
Agents see only name and description until they load the skill, so the description decides whether it is ever used.
Optional keys: user-invocable, argument-hint, compatibility, disable-model-invocation, metadata.
Token Budget
- Keep the
SKILL.mdbody under 500 lines. - If it grows past that, use progressive disclosure: keep the overview and core rules in
SKILL.mdand move detail intoreferences/<topic>.mdfiles. - Link each reference file directly from
SKILL.md(one level deep) and say when to read it, so agents load it only when needed.
Public Skills
The release pipeline copies skills/ into the published igniteui-react package, and users copy single skill folders into their own agent directories. So for skills under skills/:
- Keep relative links inside
skills/: to the skill's ownreferences/files or to a sibling skill as../<name>/SKILL.md. Link anything else in this repository by its absolute GitHub URL. - Treat renaming a public skill or moving its files as a breaking change for users who installed it, and say so in
CHANGELOG.md. - Record every user-visible change to a public skill under
## UnreleasedinCHANGELOG.md.
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.
- 17d ago First seen · 56 lines · 163 tokens per session scan A 2bd2edd229bb
skill-authoring is a skill published in the GitHub repository IgniteUI/igniteui-react (56 stars, last pushed 3d ago), licensed MIT. It adds 163 tokens to every session and 887 once invoked, about $0.0007 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-09-29.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
chakra-ui-migrate
Migrate Chakra UI projects from v2 to v3, covering package changes, codemods, provider setup, color mode, prop renaming, compound components, theming, recipes, and Next.js updates. Use this skill whenever a user is upgrading Chakra UI versions, encountering breaking changes after an upgrade, converting old v2 patterns…
chakra-ui-refactor
Review, convert, and improve UI code using Chakra UI v3. Use this skill whenever a user wants to review Chakra UI code for issues, convert plain HTML/CSS, Tailwind, CSS Modules, or styled-components to Chakra UI, clean up messy Chakra components, fix layout structure or token usage, or asks anything like "is this…
material-ui-nextjs
Integrates Material UI with Next.js App and Pages routers using @mui/material-nextjs, Emotion cache providers, next/font, CSS layers with Tailwind/CSS Modules, Link component prop patterns, CSS theme variables SSR notes, and App Router useSearchParams + Suspense. Use when setting up or debugging MUI in a Next.js app.
material-ui-theming
Guides Material UI theming and design tokens (createTheme, ThemeProvider, palette, colorSchemes, cssVariables, theme.vars, dark mode, TypeScript augmentation). Use when building or extending a theme, toggling light/dark, or aligning tokens across an app.
material-ui-styling
Chooses the right Material UI styling approach (sx, styled, theme overrides, global CSS) from official MUI guidance. Use when styling @mui/material components, customizing themes, overriding slots, or comparing sx vs styled.