Borrowing it
Nothing to install: this file belongs to islamulhaq2811/Computer-control-MCP. 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/islamulhaq2811/Computer-control-MCP/main/.claude/skills/windows-mcp-tool-tester/SKILL.mdgit clone --depth 1 https://github.com/islamulhaq2811/Computer-control-MCPWrote 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/islamulhaq2811/computer-control-mcp/windows-mcp-tool-tester)<a href="https://agentmods.dev/skills/islamulhaq2811/computer-control-mcp/windows-mcp-tool-tester"><img src="https://agentmods.dev/badge/skills/islamulhaq2811/computer-control-mcp/windows-mcp-tool-tester/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/islamulhaq2811/computer-control-mcp/windows-mcp-tool-tester"><img src="https://agentmods.dev/badge/skills/islamulhaq2811/computer-control-mcp/windows-mcp-tool-tester.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.00139 | $0.06451 |
| Opus 5 | $0.00069 | $0.03225 |
| Sonnet 5 | $0.00028 | $0.01290 |
| Haiku 4.5 | $0.00014 | $0.00645 |
Grade A, and why
windows-mcp-tool-tester 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 11d 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.
This is a copy
100% identical to windows-mcp-tool-tester — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 586 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Windows-MCP Tool Tester
An automated testing skill that generates comprehensive test cases for a single Windows-MCP tool, executes them, and produces a structured test report with pass/fail results, performance metrics, and actionable recommendations.
Core Principles
- One tool per invocation. If the user doesn't specify which tool to test, ask them before proceeding.
- Black-box testing only. Derive test cases exclusively from the MCP tool description and parameter schema — never read source code. Silence in the schema is a documentation gap, not a testing hint.
- Auto-generate test cases from the tool's MCP description and parameter schema. Cover common scenarios, edge cases, parameter combinations, and error handling paths.
- Measure two dimensions: correctness (return value matches expectations) and response time (end-to-end, including MCP overhead).
- Mandatory side-effect verification: every tool call that may modify system state MUST be independently verified — no exceptions, no sampling.
- Safe cleanup: track process PIDs spawned during testing; only kill those specific PIDs during teardown, never kill by process name alone.
- Safety first: Windows-MCP has full system access with no sandboxing. Tests involving
destructive tools (FileSystem delete, Registry set/delete, Process kill, PowerShell) can
modify or destroy data. Running in a VM or Windows Sandbox is strongly recommended.
Before executing destructive test cases, confirm the user accepts the risk. See
SECURITY.md. - Produce a structured report at the end (see Step 4).
Step 0: Identify the Target Tool
If the user hasn't specified a tool, present the full list and ask them to pick one:
App, PowerShell, Screenshot, Snapshot, Click, Type, Scroll, Move, Shortcut, Wait, MultiSelect, MultiEdit, Clipboard, Process, Notification, FileSystem, Registry, Scrape
Once a tool is confirmed, proceed to Step 1. Do NOT test multiple tools in one session.
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.
- 11d ago First seen · 586 lines · 139 tokens per session scan A df6dfb97f7b3
windows-mcp-tool-tester is a skill published in the GitHub repository islamulhaq2811/Computer-control-MCP (0 stars, last pushed 22d ago), licensed MIT. It adds 139 tokens to every session and 6,451 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to windows-mcp-tool-tester, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.