Borrowing it
Nothing to install: this file belongs to Vinayreddy18/MCP_for_Windows. 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/Vinayreddy18/MCP_for_Windows/main/.claude/skills/windows-mcp-tool-tester/SKILL.mdgit clone --depth 1 https://github.com/Vinayreddy18/MCP_for_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/vinayreddy18/mcp_for_windows/windows-mcp-tool-tester)<a href="https://agentmods.dev/skills/vinayreddy18/mcp_for_windows/windows-mcp-tool-tester"><img src="https://agentmods.dev/badge/skills/vinayreddy18/mcp_for_windows/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/vinayreddy18/mcp_for_windows/windows-mcp-tool-tester"><img src="https://agentmods.dev/badge/skills/vinayreddy18/mcp_for_windows/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.5 | $0.00056 | $0.02580 |
| Sonnet 5.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 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.
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.
- 1mo ago First seen · 586 lines · 139 tokens per session scan A df6dfb97f7b3
windows-mcp-tool-tester is a skill published in the GitHub repository Vinayreddy18/MCP_for_Windows (1 stars, last pushed 1mo ago), licensed MIT. It adds 139 tokens to every session and 6,451 once invoked, about $0.0006 per session on Opus 5.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
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
critique
Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.