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 travisjneuman/.claude --skill computer-usegit clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/travisjneuman/.claude/computer-use)<a href="https://agentmods.dev/skills/travisjneuman/.claude/computer-use"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/computer-use/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/travisjneuman/.claude/computer-use"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/computer-use.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.00203 | $0.02047 |
| Opus 5.5 | $0.00081 | $0.00819 |
| Sonnet 5.5 | $0.00041 | $0.00409 |
| Haiku 4.5 | $0.00020 | $0.00205 |
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 today.
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 computer-use — 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Computer use (desktop control)
Computer use lets Claude take screenshots of the person's desktop and control it with mouse clicks, keyboard input, and scrolling, through the Claude desktop app. Its tools are named mcp__computer-use__* (for example request_access, screenshot) when the session runs inside the desktop app, and mcp__remote-devices__computer_* (for example computer_request_access, computer_screenshot) when the session runs in the cloud and is linked to the person's computer. Computer use works only while Computer use is turned on in the Claude desktop app (Settings → This computer → Computer use; it is off by default).
Turning computer use on from a chat
What Claude does first depends on which tools are present (loaded or deferred):
- Computer-use tools are present. Claude goes straight to the access flow below.
- No computer-use tools, but an
enable__mcp__remote-devices__computertool is present. Claude calls that tool once, before any other step of the task, with the task in itstaskfield. When the call goes through, themcp__remote-devices__computer_*tools arrive with it and Claude starts with the access flow below; there is no second enable step. If it does not go through, Claude relays the reason in one line and carries on with what it can do in the conversation. - Neither. Computer use is not available in this conversation as it stands, and Claude says so plainly without diagnosing why: in general Claude can use apps on a computer where the Claude desktop app is installed and signed in with Computer use turned on, and on claude.ai in a web browser, if the composer's + menu offers Devices, the person can pick their computer there before sending a new message. Claude does not pretend to act.
Separate filesystems
Computer-use actions (clicks, typing, clipboard writes) happen on the person's real computer, a different system from wherever Claude's own shell and files are, when it has them. Files Claude creates on its side do not exist on the person's machine. If Claude puts a command or file path in the person's clipboard, or types into one of their apps, the path must exist on their computer, not a path on Claude's side that they can't reach.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 68 lines · 203 tokens per session scan A f1b16578da1e
computer-use is a skill published in the GitHub repository travisjneuman/.claude (101 stars, last pushed today), licensed MIT. It adds 203 tokens to every session and 2,047 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to computer-use, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
application-pack
Turns one pasted job post into an application folder built only from the student's own career vault: a tailored resume, a cover letter under 250 words, and an HR call sheet with the answers already drafted. Reads career-vault/01 to 06 first and refuses to run while the positioning, portfolio story or resume are still…
Scheduler
Create and manage scheduled tasks with cron, interval, or one-time execution.
Slack
Search messages, manage channels, reactions, pins, and users in Slack.
session-handoff
Claude Code Session Handoff: structured context export/import between sessions, state serialization, continuation prompts, cross-session knowledge transfer, and resumable workflows.
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.