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 sbroenne/mcp-windows --skill windows-cligit clone --depth 1 https://github.com/sbroenne/mcp-windowsWrote 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/sbroenne/mcp-windows/windows-cli)<a href="https://agentmods.dev/skills/sbroenne/mcp-windows/windows-cli"><img src="https://agentmods.dev/badge/skills/sbroenne/mcp-windows/windows-cli/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/sbroenne/mcp-windows/windows-cli"><img src="https://agentmods.dev/badge/skills/sbroenne/mcp-windows/windows-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.01639 |
| Opus 5.5 | $0.00020 | $0.00656 |
| Sonnet 5.5 | $0.00010 | $0.00328 |
| Haiku 4.5 | $0.00005 | $0.00164 |
Grade A, and why
windows-cli 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 18d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
wincli is the command-line twin of the Windows MCP server. Every command calls the exact same
underlying tool through a persistent user-owned CLI daemon. When you already have
a shell, discover only the commands you need instead of loading every MCP tool schema.
The context saving depends on the host's tool-loading behavior.
IDs from CLI discovery can be reused across commands against that daemon.
MCP instances have separate owners; never transfer their IDs to the CLI.
Discovery (do this first)
wincli --help- the command map and a common workflow.wincli tools- every command with its options.wincli tools --json- machine-readable tool manifest (names, descriptions, JSON input schemas); the same surface the MCP server exposes viatools/list, not a CLI flag schema. Usetoolsfor kebab-case CLI spellings.wincli guidance- CLI lifetime limitations followed by the shared semantic-automation guide.
Preferred workflow
- Observe existing windows with
wincli window find --title <part>or launch withwincli app --path <exe>. InspectlaunchStatusandwindow/windows: the handle may be missing or ambiguous. Inspect candidates or rediscover withwindow find; do not continue with handle-based commands until the intended target is identified.possibleHandoffdoes not confirm delivery or loaded content; verify the intended page/document before acting. wincli ui snapshot --window <handle> --mode autoto see controls and establish a baseline for repeated observations.wincli ui find|click|type|select|read --window <handle> ...for normal controls.wincli ui read-table --window <handle> --element-id <grid-id>to pull an observed grid/table into structured rows + headers. For a web page, add--format articletowincli ui readto get clean main-content text (nav/breadcrumb chrome and inline link URLs stripped, headings/lists as markdown).wincli file-save --window <handle> --path <file>for supported Save / Save As dialogs. Usewincli file-open --window <handle> --path <file>for Open flows. Inspect remaining dialogs after failure orconfirmation_required. Choose any confirmation, cancellation, or correction explicitly; do not automatically repeat the helper.wincli clipboard get|set|clearfor fast bulk text IO; keep reusableui batchsteps in project JSON files and run them with--steps-file.- Fall back to
wincli screenshot,wincli mouse, orwincli keyboardonly for custom-drawn UI.
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.
- 18d ago Changed · +11 lines 4861ec815b28
- 20d ago Changed 934cad1b5e57
- 21d ago Changed · +4 lines ae9b3bd7009d
- 1mo ago Changed · +23 lines 9df4bce34cf4
- 1mo ago First seen · 75 lines · 51 tokens per session scan A a5c2f209406c
windows-cli is a skill published in the GitHub repository sbroenne/mcp-windows (117 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 1,639 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-08-30.
Other skills, from other repositories
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…
xtwitter-scraper
Use XTwitterScraper when a .NET application needs typed access to Xquik's X automation REST API for tweet search, user lookup, posting workflows, extraction jobs, monitors, webhooks, or giveaway draws. USE FOR: integrating the XTwitterScraper NuGet package; reviewing Xquik API client usage; modeling API-key…
playwright-visual-testing
Add, repair, or review Playwright visual regression tests for browser-facing .NET apps, including screenshot baselines, Pixelmatch thresholds, deterministic rendering, and GitHub Actions artifacts. USE FOR: toHaveScreenshot, page.screenshot visual checks, Pixelmatch/pngjs comparison scripts, visual baseline updates…
playwright-cli
Drive a live browser from the CLI with playwright-cli to navigate, interact, snapshot, and capture evidence. Use for ad-hoc browser commands, page inspection, screenshots, traces, network mocking, session management, or interactive debugging—not authoring @playwright/test specs. Keywords: playwright-cli, browser…
webapp-selenium-testing
Author and maintain versioned Selenium WebDriver tests with Java and JUnit 5. Use for creating, debugging, or running Selenium specs, implementing Page Objects, handling explicit waits, capturing screenshots, or setting up Maven test projects. Supports Chrome, Firefox, and Edge. Keywords: Selenium WebDriver, Java…
lightcad
Use when building or extending a desktop CAD/BIM application with the open-source FeiYang LightCAD platform — plugin development, custom elements, DWG/DXF I/O, 2D drafting and 3D/BIM modeling on C#/.NET. LightCAD (FeiYang Integrated Design Platform) is a C# CAD system integrating 2D design, 3D design, and BIM.