winapp CLI is a command-line tool for Windows application development that manages SDKs, app identity, manifests, certificates, packaging, and build tools. It helps developers using frameworks such as .NET, Win32, CMake, Electron, or Rust access Windows-native development capabilities. The catalogue add-ons provide agent workflows for using the CLI.
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 microsoft/winappCli --skill winui-designgit clone --depth 1 https://github.com/microsoft/winappCliWrote 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/microsoft/winappcli/winui-design)<a href="https://agentmods.dev/skills/microsoft/winappcli/winui-design"><img src="https://agentmods.dev/badge/skills/microsoft/winappcli/winui-design/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/microsoft/winappcli/winui-design"><img src="https://agentmods.dev/badge/skills/microsoft/winappcli/winui-design.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.00070 | $0.03169 |
| Opus 5.5 | $0.00028 | $0.01268 |
| Sonnet 5.5 | $0.00014 | $0.00634 |
| Haiku 4.5 | $0.00007 | $0.00317 |
Grade A, and why
winui-design 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 7d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope: WinUI 3 apps only. The Windows App SDK is not WinUI. A WPF, WinForms, Electron, or other app that references the Windows App SDK (for notifications, packaging, or other APIs) is not a WinUI app; keep its framework and don't apply this skill unless the task is to port it to WinUI 3. A WinUI 3 project has <UseWinUI>true</UseWinUI> or uses Microsoft.UI.Xaml.
Search samples before writing XAML
This workflow requires WinApp CLI 0.7+. Use winapp find-ui for grounded control and sample discovery. Front-load lookups, then code:
winapp find-ui "<focused feature>" # compact matches + scenario IDs
winapp find-ui --id <scenario-id> # full XAML/C# + prerequisite notes
winapp find-ui --id <id-1> --id <id-2> --json # batch, structured output
winapp find-ui --list # browse all default-source scenarios
winapp find-ui "<feature>" --refresh # force a corpus refresh
Default search covers the WinUI Gallery, Windows Community Toolkit, and curated core patterns. Reactor's C#-only/MVU samples are opt-in with --source reactor; use them only for Reactor projects. The Gallery/Toolkit/Reactor corpus is fetched and cached by WinApp CLI, while core patterns work offline.
Verify APIs against the restored project
Before coding API assumptions, run from the restored app project directory so winapp find-api uses its exact references, not a sample's possibly newer package versions:
winapp find-api InfoBar --json --project-dir .
winapp find-api check-property InfoBar Severity IsOpen Message Title --json --project-dir .
winapp find-api members NavigationView --filter selected --json --project-dir .
Use either --project-dir <app-directory> (defaults to cwd) or --project <name> to select among multiple projects, never both. An unscoped query from a repo root or sibling project may target the wrong API surface. --project sdk searches only the installed machine SDK, not the app's NuGet references. If results look stale, check restore/project selection before refreshing. Use winapp find-api --help for discovery/index commands rather than guessing an API from memory; use find-ui for the usage pattern.
What ships with it
3 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.
- 7d ago Changed · -29 tokens per session 4d741256e7e1
- 9d ago First seen · 190 lines · 99 tokens per session scan A 3bd47be91b17
winui-design is a skill published in the GitHub repository microsoft/winappCli (1,314 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 3,169 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-07.
Other skills, from other repositories
brand-identity
Use when a project needs its visual foundation built or consolidated into one system: logo brief, color system in HEX/RGB/CMYK/OKLCH with proven AA contrast, type system, usage rules, and an exported W3C design-tokens.json that later skills consume. NOT the applied UI pixels (that is design), NOT the words or tone…
quicker-browser-script
End-to-end webpage scripting via the Quicker browser extension: prototype RunScript live (userbrowser / chromecontrol), save as a sys:chromecontrol action, then auto-run it with event triggers (quickertrigger, e.g. BrowserUrlChanged). Use when the user wants scripts to run on pages automatically.
create-canvas
Create a project Copilot extension canvas for the current workspace.
frontend
Builds, styles, and polishes web UI and UX. Use for any frontend, page, component, styling, layout, animation, or visual-quality task, or when asked to make an interface look or feel a certain way.
cli-anything-photoshop
A command-line tool that controls Adobe Photoshop through Windows automation. It can work with Photoshop documents, layers, selections, text, image adjustments, and exports.
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.