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 agentmods add mcp/twh66666/codex-computer-use-for-windows/windows-computer-usegit clone --depth 1 https://github.com/twh66666/codex-computer-use-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/mcp/twh66666/codex-computer-use-for-windows/windows-computer-use)<a href="https://agentmods.dev/mcp/twh66666/codex-computer-use-for-windows/windows-computer-use"><img src="https://agentmods.dev/badge/mcp/twh66666/codex-computer-use-for-windows/windows-computer-use.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
windows-computer-use 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 5d 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.
What it actually says
{
"windows-computer-use": {
"command": "C:\\Windows\\System32\\cmd.exe",
"args": [
"/d",
"/c",
"__PLUGIN_ROOT__\\scripts\\run_windows_computer_use_mcp.cmd"
]
}
}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.
- 5d ago First seen · 10 lines scan A 6152d088d3fa
windows-computer-use is an MCP server published in the GitHub repository twh66666/codex-computer-use-for-windows (10 stars, last pushed 4mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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 mcp servers, from other repositories
oysterworkflow
MCP server "oysterworkflow" as configured in ShuxinYang111/oysterworkflow. Runs ./mcp/server.mjs with node.
oswright
Playwright-like automation framework for the operating system. Runs locally from the oswright Python package.
kimi-computer-use
MCP bridge for using an existing OpenAI Computer Use installation from Kimi Code CLI on macOS. Runs locally from the kimi-computer-use npm package.
screen-use
MCP server "screen-use" as configured in tongriyaotxt/screen-use. Runs locally from the screen-use Python package.
claude-codex-computer-use
MCP bridge for using an existing OpenAI Computer Use installation from Claude Code on macOS. Runs locally from the claude-codex-computer-use npm package.
fast-hands-mcp
Local-first cross-platform execution and research layer for AI agents with persistent PowerShell, durable checkpoints, live operator control, optional Windows UI, web research and YouTube research. Runs locally from the fast-hands-mcp npm package.