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 winapp-performancegit 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/winapp-performance)<a href="https://agentmods.dev/skills/microsoft/winappcli/winapp-performance"><img src="https://agentmods.dev/badge/skills/microsoft/winappcli/winapp-performance/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/winapp-performance"><img src="https://agentmods.dev/badge/skills/microsoft/winappcli/winapp-performance.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.00046 | $0.01216 |
| Opus 5.5 | $0.00018 | $0.00486 |
| Sonnet 5.5 | $0.00009 | $0.00243 |
| Haiku 4.5 | $0.00005 | $0.00122 |
Grade A, and why
winapp-performance 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 2d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow
- Read the WinUI performance guide for capture limits, query options, partial-result handling, privacy and interpretation.
- Use the existing app PID when possible. Start with
winapp perf start --app <pid> --output <empty-directory> --json.--appalso accepts a process name or window title using the same matching rules aswinapp ui. Use the returnedtarget.pidfor subsequent UI actions. For a new launch, usewinapp run <project> --profile <empty-directory> --detach --json. This records after launch, which is enough for navigation, scrolling and other post-launch scenarios. For startup investigations only, add--profile-mode elevated(one UAC prompt for the recorder, which the user must approve) and checkProfile.StartupCoverage; see the guide's startup workflow. Do not add startup delays or replace a generatedMain. - Wait for successful recording readiness. Save the returned capture ID.
- Mark the beginning with
winapp perf mark <id> --name scenario-start --json, drive a short repeatable scenario with verified UI selectors, wait for its visible outcome, then runwinapp perf mark <id> --name scenario-end --json. - Run
winapp perf stop <id> --jsonbefore closing the app. - Start with
winapp perf analyze <directory> --from-marker scenario-start --to-marker scenario-end --jsonto compare mutually exclusive primary-UI-thread activity, the hottest parsed XAML resources, and the detailed operation ranking. Use--view parsingover the same range when the parsing preview needs full paging. Then querywinapp perf analyze <directory> --view hotspots --from-marker scenario-start --to-marker scenario-end --json; its default threshold is 16.67 ms and each row includes dominant direct child operations. Expand a returned operation with--view call --id <call-id> --depth 2 --from-marker scenario-start --to-marker scenario-end --json. Use--view calls --family layoutwith the same marker range when the hotspot evidence points to layout. Query--view gc --sort durationover the same marker range to find the longest collection and suspension intervals, then inspect referenced interval IDs. Use element and event views for source and evidence drill-down. FollownextOffset; do not dump NDJSON or ETL into context. For overall resource cost, use--view resourcesover the same marker range; see the guide's process counters. For app-side composition, query--view calls --family compositionand--view events --event DCompDeviceCommitover the same marker range; see composition submission. - Report observed cost, supporting event IDs, coverage gaps, and one concrete next experiment. Preserve stdout when partial results accompany a nonzero exit code.
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.
- 2d ago First seen · 78 lines · 46 tokens per session scan A 1bd52d8ac68b
winapp-performance is a skill published in the GitHub repository microsoft/winappCli (1,314 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 1,216 once invoked, about $0.0002 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-14.
Other skills, from other repositories
quicker-run
Use when running or debugging Quicker actions via qkrpc MCP (not editing program body).
code_explorer
Explores the repository to locate primary source files, coupled UI components, and test files for bug reports or feature requests.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
feedback
Skill "feedback" from Hmbown/Codewhale, covering feedback, when to use, setup, workflow and non-goals.
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
smiles-validation
Strict SMILES validation, structural comparison, and modification verification. Catches invalid LLM-generated molecules.