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.
Borrowing it
Nothing to install: this file belongs to microsoft/winappCli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/microsoft/winappCli/main/.github/skills/code-quality/SKILL.mdgit 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/code-quality)<a href="https://agentmods.dev/skills/microsoft/winappcli/code-quality"><img src="https://agentmods.dev/badge/skills/microsoft/winappcli/code-quality/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/code-quality"><img src="https://agentmods.dev/badge/skills/microsoft/winappcli/code-quality.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.00147 | $0.03566 |
| Opus 5.5 | $0.00059 | $0.01426 |
| Sonnet 5.5 | $0.00029 | $0.00713 |
| Haiku 4.5 | $0.00015 | $0.00357 |
Grade A, and why
code-quality 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 24d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the local code-quality pre-check for microsoft/winappcli. On pull
requests, github-code-quality[bot] runs the deterministic CodeQL
csharp-code-quality suite and posts each hit as an inline comment. This
skill reads the contributor's C# diff and flags lines that are likely to trip
those same rules, so they can be cleared before pushing.
Scope is C# only — the language the bot rule-checks in this repo.
Be honest about what this is. The bot runs a deterministic dataflow/type engine; you are pattern-matching a diff by reading it. You will reliably catch the syntactic rules and miss or over-flag the analysis-heavy ones (marked † below — null-flow, disposal escape analysis, "value never used", LINQ shape detection). Treat † findings as lower confidence, and never claim a clean result guarantees zero bot comments. It does not — it means nothing obvious is left. This also does not cover the bot's separate AI-powered pass, or C/C++.
Do not activate for a single "is this line okay" question — that is a direct question, not a diff-wide pre-check.
1. Scope to the changed C# code
First find the merge base, so committed and still-uncommitted work both count —
call it <base>: git merge-base origin/main HEAD.
- Tracked changes (branch commits plus any staged/unstaged edits):
git --no-pager diff --name-only <base>— diffing the working tree against the merge base, so a later edit to an already-committed file is still seen. - Untracked new files:
git ls-files --others --exclude-standard -- "src/*.cs"—git diffcannot emit hunks for these; read them directly withview.
Keep only *.cs under src\, and drop files matching the repo's CodeQL exclusion
**/*Tests/*.cs — a .cs file directly inside a directory whose name ends in
Tests (e.g. src\WinApp.Cli.Tests\Foo.cs). Mirror that glob exactly: a file
nested deeper, such as src\...\WinApp.Cli.Tests\TestApps\App.xaml.cs, does not
match it, so the bot may scan it — keep those in scope. If nothing survives, say
so and stop.
Then read the changed lines. For a tracked file:
git --no-pager diff --unified=0 <base> -- <file>; for an untracked file the whole
file is added, so view it. Either way view each changed region for context.
Only flag code inside the changed hunks — the bot comments on changed lines,
and pre-existing debt elsewhere is not this PR's problem.
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.
- 24d ago First seen · 217 lines · 147 tokens per session scan A c984ab640184
code-quality is a skill published in the GitHub repository microsoft/winappCli (1,314 stars, last pushed today), licensed MIT. It adds 147 tokens to every session and 3,566 once invoked, about $0.0006 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-22.
Other skills, from other repositories
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…
swarm-pr-review
Run a graph-guided, tool-augmented PR review using context packing, parallel exploration, mandatory repository-agnostic risk-family coverage with dispatch scaled to diff size and risk, independent reviewer validation, critic challenge, and metrics writeback. Use for deep pull request review with low false-positive…
code-review
You are a senior code reviewer. You receive diffs via stdin.
include-test-files-that-assert-on-behavior-being-changed-in-decl
When delegating a task affected by this skill, include.
review
Adversarial fresh-context review and risk check of an increment before it ships; every finding cites path:line and is re-verified. Use for "review", "qa", "quality check", "critique this".
tech-debt-ci-review
Codex adapter for deep technical-debt and CI-stability audits. Use when asked to find test theater, flaky tests, missing or mis-scoped tests, brittle CI/toolchain behavior, structural debt blocking green PRs, or a remediation order for opencode-swarm.