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/minghinmatthewlam/computer-use-mcp/agents-mdgit clone --depth 1 https://github.com/minghinmatthewlam/computer-use-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/minghinmatthewlam/computer-use-mcp/agents-md)<a href="https://agentmods.dev/instructions/minghinmatthewlam/computer-use-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/minghinmatthewlam/computer-use-mcp/agents-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.00978 | $0.00978 |
| Opus 5 | $0.00489 | $0.00489 |
| Sonnet 5 | $0.00196 | $0.00196 |
| Haiku 4.5 | $0.00098 | $0.00098 |
Grade A, and why
computer-use-mcp AGENTS.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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Guidelines
This repo exposes live macOS computer-use capabilities. Treat runtime changes as safety-sensitive even when they look like ordinary Swift edits.
Safety Boundaries
- Do not run live GUI, TCC, app-control, clipboard, or global-cursor demos unless the user explicitly approves that run.
- Default to non-mutating verification:
swift build,swift test, and CLI help/version/health_report --jsonsmoke checks. - Treat
scripts/e2e_demo.py,doctor --prompt,call,serveagainst real apps, and any test using Accessibility, Screen Recording, clipboard, window management, or input delivery as mutating/local-only. - Never disable safety gates (
COMPUTER_USE_MCP_NO_SAFETY=1), app leases, or daemon isolation to make a test pass unless the task is specifically about those controls and the final result verifies the safe default path too.
Command Discipline
- Run each shell command as a separate tool call. Do not chain with
&&,||,;, or pipes unless that shell behavior is the thing being tested. - Prefer
rg/rg --filesfor discovery. - Do not push, publish, rewrite history, delete user data, or kill unrelated processes without explicit permission.
Ownership Map
- Entry / wiring (
main.swift,Serve.swift,Dispatch.swift,Call.swift,Doctor.swift,HealthReport.swift,Version.swift): subcommand routing, MCP stdio shim, shared dispatch funnel (rate limit + logging), CLIcallharness, TCC doctor / structured health report, and the binary version stamp. Sources/computer-use-mcp/Core/: capture, AX, input, targeting, policy, and config. Runtime or safety changes here require focused unit coverage plus a local real-surface verification plan.Sources/computer-use-mcp/Tools/: MCP tool handlers and catalog. Keep schemas stable and verify CLI/MCP smoke behavior when changing contracts.Sources/computer-use-mcp/Daemon/: shared engine process, socket protocol, and app leases. Verify multi-session and daemon fail-fast assumptions before claiming concurrency safety; when touching leases or the socket path, confirm concurrent sessions cannot interleave inside one app and that mutating tools cannot bypass daemon arbitration through in-process fallback.Sources/computer-use-mcp/Overlay/: visible agent cursor. Keep it optional for headless/CI paths.Sources/computer-use-mcp/ToolKit/: schema/tool-spec plumbing. Prefer small, backwards-compatible changes.Sources/ComputerUseFixture/: deterministic AppKit truth-suite fixture (honest / liar controls, web pane, dense table) used by the release battery — seedocs/fixture-app.md.Tests/ComputerUseMCPTests/: pure unit tests only. Do not add live GUI/TCC tests to the default suite.scripts/: local demos and manual preflight helpers. Document required user consent and side effects..github/workflows/: hosted CI. Keep it deterministic and avoid live GUI/TCC requirements on hosted runners.
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 · 79 lines · 978 tokens per session scan A 53062e78a36b
computer-use-mcp AGENTS.md is an instructions file published in the GitHub repository minghinmatthewlam/computer-use-mcp (45 stars, last pushed 18d ago), licensed MIT. It adds 978 tokens to every session, about $0.0049 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-30.
Other instructions, from other repositories
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.