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 metahub-tech/agent-fleet --skill using-wingit clone --depth 1 https://github.com/metahub-tech/agent-fleetWrote 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/metahub-tech/agent-fleet/using-win)<a href="https://agentmods.dev/skills/metahub-tech/agent-fleet/using-win"><img src="https://agentmods.dev/badge/skills/metahub-tech/agent-fleet/using-win/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/metahub-tech/agent-fleet/using-win"><img src="https://agentmods.dev/badge/skills/metahub-tech/agent-fleet/using-win.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.00048 | $0.01689 |
| Opus 5.5 | $0.00019 | $0.00676 |
| Sonnet 5.5 | $0.00010 | $0.00338 |
| Haiku 4.5 | $0.00005 | $0.00169 |
Grade A, and why
using-win 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 1mo 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using win-device
Drive a remote Windows test machine via the win-device MCP server (FastMCP, streamable-http on Tailscale). Multi-client native; advisory single-holder coordination; 42 tools spanning state / screen / window / mouse / keyboard / process / file / search / shell.
Critical patterns
Screenshot click coordinates are SCREEN pixels, NOT image-display pixels
take_screenshot returns a PNG of the actual screen (e.g. 1920x1080). The viewer rendering it (Read tool, image preview, etc.) MAY downscale to a smaller display size like 960x540. Always pass click coordinates in actual screen pixels.
get_screen_size # returns {"width": 1920, "height": 1080}
take_screenshot # PNG of full screen; rendered display may be smaller
tap(x=1096, y=600) # x,y MUST be in 1920x1080 space
If taps miss: the displayed image is a thumbnail, not the source of truth. Call get_screen_size first; reason about coordinates in that coordinate system.
UI introspection and app lifecycle
dump_ui() # UI-Automation tree of the foreground window
find_elements(query="Save") # locate elements by UIA attributes -> ranked candidates + center coords
tap_element(query="Save") # find + click an element's live center
inspect_window(...) # richer per-window introspection (platform extension)
terminate_app(target="notepad.exe") # terminate by process name / path substring
kill_process(pid=...) # kill by PID (platform extension)
dump_ui, find_elements / tap_element, and terminate_app are the canonical cross-platform tools. inspect_window (richer window introspection) and kill_process (PID-based kill) remain as Windows-specific extensions for finer control.
Element-first, screenshot as fallback
Prefer find_elements / tap_element(query) over hardcoded tap(x, y). Element location queries the live UIA tree by accessibility attributes (name / automation-id / control-type), so it survives layout / scroll / resolution drift that breaks fixed coordinates.
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.
- 1mo ago First seen · 120 lines · 48 tokens per session scan A de4d18a02c7b
using-win is a skill published in the GitHub repository metahub-tech/agent-fleet (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 48 tokens to every session and 1,689 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-31.
Other skills, from other repositories
langbot-testing
Test LangBot WebUI and core product flows with an automated browser and backend logs. Use when validating the configured LangBot frontend, pipeline Debug Chat, model provider setup and test buttons, bot and knowledge-base UI flows, or troubleshooting failed LangBot end-to-end tests.
web-ui-test
Test the IronClaw web UI using the Claude for Chrome browser extension.
webqa
Use WebQA to test websites, web pages, URLs, login flows, search flows, forms, navigation, and core user journeys with an AI browser QA agent.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
browser-testing-with-devtools
Tests in real browsers. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data via Chrome DevTools MCP.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.