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 skills add zavora-ai/computer-use-mcp --skill computer-usegit clone --depth 1 https://github.com/zavora-ai/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/skills/zavora-ai/computer-use-mcp/computer-use)<a href="https://agentmods.dev/skills/zavora-ai/computer-use-mcp/computer-use"><img src="https://agentmods.dev/badge/skills/zavora-ai/computer-use-mcp/computer-use.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.00319 |
| Opus 5 | $0.00018 | $0.00160 |
| Sonnet 5 | $0.00007 | $0.00064 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
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 8d 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
Computer Use (desktop automation)
When to use
- Native desktop apps, installers, modal dialogs, simulators
- UI-only workflows with no API/CLI
When NOT to use
- Prefer connectors, shell, filesystem, or browser automation (Playwright) first
Mandatory first steps
get_tool_guide({ task_description })— pick scripting vs AX vs coordinatesget_app_capabilities({ bundle_id })— is the app scriptable/accessible/running?- Prefer
run_script→ accessibility (fill_form,click_element) →left_click/typelast
Hard rules
- Always set
target_app(bundle ID macOS / process name Windows) ortarget_window_id - Do not screenshot every step; use
get_ui_tree/find_elementfor structure - Long text:
write_clipboard+ paste shortcut, nottype - On focus failure, follow
suggestedRecovery(activate_window,unhide_app,open_application) - Use
focus_strategy: "prepare_display"only after a focus race
Safety
- Destructive:
process_kill, filesystem delete/write, registry set/delete,run_script - Sensitive apps may need
approval_tokenor host elicitation
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.
- 8d ago First seen · 30 lines · 36 tokens per session scan A 4228d8fa8a4f
computer-use is a skill published in the GitHub repository zavora-ai/computer-use-mcp (45 stars, last pushed 16d ago), licensed MIT. It adds 36 tokens to every session and 319 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…