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 instructions/shikechen01/windowspc-mcp/claude-mdgit clone --depth 1 https://github.com/ShikeChen01/WindowsPC-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/instructions/shikechen01/windowspc-mcp/claude-md)<a href="https://agentmods.dev/instructions/shikechen01/windowspc-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/shikechen01/windowspc-mcp/claude-md.svg" alt="Measured on agentmods" 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 | $0.01768 | $0.01768 |
| Opus 5 | $0.00884 | $0.00884 |
| Sonnet 5 | $0.00354 | $0.00354 |
| Haiku 4.5 | $0.00177 | $0.00177 |
Grade A, and why
WindowsPC-MCP CLAUDE.md 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.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What This Is
WindowsPC-MCP is a FastMCP server that confines an AI agent's GUI interaction to a Parsec VDD virtual display. The agent gets its own screen with independent cursor/focus — it can only click/type/scroll on its virtual display, but can read all screens for context. As of v0.6.0, a PyQt6 control UI auto-launches alongside the server so the human user can monitor and intervene (Pause / Resume / Join / Stop / Screen-select).
Commands
# Install (PyQt6 mandatory as of v0.6.0)
pip install -e ".[dev]"
# Build the DXGI capture DLL (one-time, needs cl.exe or g++)
cd src/windowspc_mcp/desktop && see BUILD_CAPTURE_DXGI.md
# Run server
windowspc-mcp --transport stdio
windowspc-mcp --transport sse --host localhost --port 8000
windowspc-mcp --no-ui # headless (CI / gateways)
# Tests (~1300 tests)
python -m pytest tests/ # all tests
python -m pytest tests/desktop/ # desktop isolation tests
python -m pytest tests/ui/ # PyQt6 UI tests (pytest-qt)
python -m pytest tests/confinement/ # confinement tests
python -m pytest tests/display/ # display driver tests
python -m pytest tests/ipc/ # IPC layer tests
python -m pytest tests/smoke/ # smoke tests (need VDD hardware)
python -m pytest tests/desktop/test_gate.py -v # single file, verbose
python -m pytest -k "test_switch_to_agent" # single test by name
# Verify UI builds + renders headlessly
python tools/ui_smoke.py tools/ui_smoke.png
# Lint
ruff check src tests
ruff check --fix src tests
Architecture
Request Flow
MCP Tool call (Click, Type, etc.)
→ guarded_tool decorator (confinement/decorators.py)
→ ToolGuard.check() (state + bounds validation)
→ ConfinementEngine.validate_and_translate() (agent-relative → absolute coords)
→ AgentInputService (input/service.py) → Win32 SendInput
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 · 127 lines · 1,768 tokens per session scan A 0543d2915adb
WindowsPC-MCP CLAUDE.md is an instructions file published in the GitHub repository ShikeChen01/WindowsPC-MCP (1 stars, last pushed 3mo ago), licensed MIT. It adds 1,768 tokens to every session, about $0.0088 per session on Opus 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).