microsoft/win-dev-skills is a collection of AI-agent instructions and tools for creating native Windows applications with WinUI 3 and the Windows App SDK. Windows developers use it to guide agents through app development tasks from scaffolding and design to testing, packaging, and release. The catalogue entries are its agents, skills, and plugin components.
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/win-dev-skills --skill windbg-kernel-verifier-triagegit clone --depth 1 https://github.com/microsoft/win-dev-skillsWrote 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/win-dev-skills/windbg-kernel-verifier-triage)<a href="https://agentmods.dev/skills/microsoft/win-dev-skills/windbg-kernel-verifier-triage"><img src="https://agentmods.dev/badge/skills/microsoft/win-dev-skills/windbg-kernel-verifier-triage/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/win-dev-skills/windbg-kernel-verifier-triage"><img src="https://agentmods.dev/badge/skills/microsoft/win-dev-skills/windbg-kernel-verifier-triage.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.00054 | $0.00972 |
| Opus 5.5 | $0.00022 | $0.00389 |
| Sonnet 5.5 | $0.00011 | $0.00194 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
windbg-kernel-verifier-triage 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 8d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Driver Verifier Triage
Load windbg-diagnostic-method first if it is not already loaded in this
conversation, and apply it throughout for evidence ranking, hypothesis testing,
confidence calibration, independent review, and report validation. This skill
adds the bug-family-specific commands and evidence requirements.
Scope
Driver Verifier checks kernel driver contracts. Application Verifier is a
different user-mode facility; use windbg-user-heap-corruption-investigation for its heap
stops. Enabled Driver Verifier flags alone do not prove a contract violation.
Use this skill when a verifier-class bugcheck or analysis identifies an actual
violation. Examples include 0xC4, 0xC9, and 0xE6; inspect the exact code
and parameters rather than treating every stop as the same family.
Workflow
1. Preserve code, subcode, and active configuration
!analyze -v
.bugcheck
!verifier
k
Record the bugcheck, subtype/subcode, offending operation and driver when reported, enabled checks, target build, and evidence availability. Decode each subcode against its documented contract. Existing output may be incomplete in a small dump; do not discard captured evidence merely because live configuration is now different.
2. Decode available I/O history
When the violation supplies an appropriate IRP address and I/O verification state is available:
!iovirp <irp-address>
!irp <irp-address>
Shadow state may preserve information lost from the live request. Correlate it
with the decoded contract and use windbg-kernel-irp-lifecycle-triage for completion,
cancellation, pending state, and ownership.
3. Recover context or follow dependencies
- Saved exception/trap context:
windbg-kernel-bugcheck-triage. - Lock-order evidence:
windbg-kernel-lock-deadlock-triage. - Outstanding or power request:
windbg-kernel-irp-lifecycle-triage.
Avoid cyclic dispatch. Carry the evidence already collected to the next skill; re-enter only when a distinct evidence requirement exists.
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.
- 8d ago First seen · 108 lines · 54 tokens per session scan A e91fef37757e
windbg-kernel-verifier-triage is a skill published in the GitHub repository microsoft/win-dev-skills (472 stars, last pushed 2d ago), licensed MIT. It adds 54 tokens to every session and 972 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-08.
Other skills, from other repositories
component-flattening-analysis
Detects misplaced classes and fixes component hierarchy problems — finds code that should belong inside a component but sits at the root level. Use when asking "clean up component structure", "find orphaned classes", "fix module hierarchy", "flatten nested components", or analyzing why namespaces have misplaced code.…
codenavi
Your pathfinder for navigating unknown codebases. Investigates with precision, implements surgically, and never assumes — if it doesn't know, it says so. Maintains a .notebook/ knowledge base that grows across sessions, turning every discovery into lasting intelligence. Summons available skills, MCPs, and docs when…
chrome-devtools
Browser debugging, performance profiling, and automation via Chrome DevTools MCP. Use when user says "debug this page", "take a screenshot", "check network requests", "profile performance", "inspect console errors", or "analyze page load". Do NOT use for full E2E test suites (use playwright-skill) or non-browser…
sentry
Inspect Sentry issues, summarize production errors, and pull health data via the Sentry API (read-only). Use when user says "check Sentry", "what errors in production?", "summarize Sentry issues", "recent crashes", or "production error report". Requires SENTRYAUTHTOKEN. Do NOT use for setting up Sentry SDK…
chrome-devtools-mcp
Use Chrome DevTools MCP from .NET agents and .NET-focused repos to inspect, debug, and automate Chrome through an MCP client. USE FOR: the repo needs browser-level debugging for ASP.NET Core, Blazor, WebAssembly, or any .NET app with a web UI; the user wants an MCP server that can inspect console. DO NOT USE FOR: pure…
managedcode-orleans-graph
Integrate ManagedCode.Orleans.Graph into an Orleans-based .NET application for grain-call policy enforcement, deadlock detection, live-call telemetry, and Mermaid graph diagnostics. USE FOR: ManagedCode.Orleans.Graph integration; allowed grain transitions; Orleans call filters; live policy graphs; reviewing Orleans…