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/devolutions/avalonia-extensions/winui-control-themingnpx skills add Devolutions/avalonia-extensions --skill winui-control-theminggit clone --depth 1 https://github.com/Devolutions/avalonia-extensionsWrote 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/devolutions/avalonia-extensions/winui-control-theming)<a href="https://agentmods.dev/skills/devolutions/avalonia-extensions/winui-control-theming"><img src="https://agentmods.dev/badge/skills/devolutions/avalonia-extensions/winui-control-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.00071 | $0.01952 |
| Opus 5 | $0.00036 | $0.00976 |
| Sonnet 5 | $0.00014 | $0.00390 |
| Haiku 4.5 | $0.00007 | $0.00195 |
Grade A, and why
winui-control-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 3d 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WinUI Control Theming
Use this skill when working on src/Devolutions.AvaloniaTheme.WinUI/ and the goal is to add or refine WinUI-styled control themes while staying consistent with the resource strategy already used for this theme.
Core Principle
Prefer official WinUI resource names over made-up local names whenever they can be identified from WinUI source or docs.
This theme should follow the WinUI model as closely as practical:
- Shared WinUI semantic tokens go in
Accents/ThemeResources.axaml - Control-specific WinUI resources go in the relevant file under
Controls/ - New local resource names should be introduced only when no real WinUI equivalent exists
Why
Avalonia's Fluent theme is a Fluent-looking base theme, but its resource surface does not always match the newer WinUI token vocabulary. For this theme, the goal is not just to make controls "look good"; it is to make them look WinUI-like using WinUI concepts and names where possible.
That keeps future control work consistent:
- later controls can reuse the same token set
- resource names stay recognizable to people familiar with WinUI
- ad-hoc local naming does not spread across the theme
Required Workflow
When adding or updating a WinUI control theme:
-
Start from the WinUI control
- Find the WinUI default template and the theme resources it uses.
- Extract the actual resource names referenced by the template.
-
Separate shared tokens from control-specific resources
- Examples of shared tokens:
TextFillColorPrimaryBrush,AccentFillColorDefaultBrush,ControlFillColorDefaultBrush - Examples of control resources:
ButtonBackground,ButtonForegroundPointerOver,ButtonBorderBrushPressed
- Examples of shared tokens:
-
Compare against Avalonia Fluent
- Check the existing Avalonia Fluent control template and resource model.
- Decide whether the control can be adapted with targeted overrides or needs a fuller template port.
-
Port only what is needed
- Do not dump the full WinUI token set into
ThemeResources.axaml. - Add only the resources that are actually referenced by the new or updated control theme, unless there is a clear near-term reason to add a small shared set together.
- Do not dump the full WinUI token set into
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.
- 3d ago First seen · 171 lines · 71 tokens per session scan A 5840daa3a161
winui-control-theming is a skill published in the GitHub repository Devolutions/avalonia-extensions (79 stars, last pushed 5d ago), licensed MIT. It adds 71 tokens to every session and 1,952 once invoked, about $0.0004 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
Shade dropdown surface contract
DropdownMenu, Select, and Popover share one visual recipe (bg-surface-elevated-2 + border-border/60 dark:border-border/30 + shadow-md). Change them together. Trigger when editing any of those three Shade files.
Shade ShadCN install
Guardrails for running pnpm dlx shadcn@latest add in Shade — never overwrite existing components, fresh branch first, swap raw colours for semantic tokens after integrating. Trigger when the user proposes a shadcn add, or when a fresh ShadCN-shaped file lands in apps/shade/src/components/ui.
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…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
better-colors
Helps you build a color system and answer anything about color in your project. You can generate palettes, use semantic tokens, convert between formats, check contrast and more.
design-frontend-dev
Clean Impeccable frontend design skill. Use when the user wants to design, redesign, critique, audit, polish, harden, optimize, adapt, clarify, colorize, animate, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, onboarding, empty states…