agent-desktop

agent-desktop is a skill for Claude Code, Codex from travisjneuman/.claude. It costs 38 tokens per session (565 once invoked), scanned A, original, MIT.

A desktop-control tool for operating native applications on macOS, Windows, and Linux through their accessibility interfaces. It works with installed desktop apps rather than web pages.

In plain words
What is it for?
It is for listing apps and windows, reading an app's controls, and clicking, typing, setting values, or pressing keys in native applications.
Why use it?
It gives an agent a structured way to inspect windows and perform actions in desktop software without using browser automation.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It is for listing apps and windows, reading an app's controls, and clicking, typing, setting values, or pressing keys in native applications.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/travisjneuman/.claude/agent-desktop
Install

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.

Any agent
npx skills add travisjneuman/.claude --skill agent-desktop
Clone the repo
git clone --depth 1 https://github.com/travisjneuman/.claude

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for agent-desktop

README.md
[![agentmods](https://agentmods.dev/badge/skills/travisjneuman/.claude/agent-desktop/github.svg)](https://agentmods.dev/skills/travisjneuman/.claude/agent-desktop)
Your own site
<a href="https://agentmods.dev/skills/travisjneuman/.claude/agent-desktop"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/agent-desktop/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.

agentmods 80×15 button for agent-desktop

Your own site · 80×15
<a href="https://agentmods.dev/skills/travisjneuman/.claude/agent-desktop"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/agent-desktop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 565 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.00565
Opus 5.5 $0.00015 $0.00226
Sonnet 5.5 $0.00008 $0.00113
Haiku 4.5 $0.00004 $0.00056

Measured today against content hash 5131334dbd0f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

agent-desktop 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.

skills/agent-desktop/SKILL.md · 40 lines

How it starts

The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Desktop

Thin guidance for vercel-labs/agent-desktop v1.0.2, an Apache-2.0 Rust shell CLI using macOS AX, Windows UI Automation, and Linux AT-SPI.

Route and prerequisites

  • If a higher-priority desktop-control tool is configured for this host (see local rules), prefer it.
  • This is a native desktop route, never a browser/source-intake route. Never scrape or drive browser web research with it.
  • If the CLI is missing, report the pinned prerequisite npm install -g [email protected]; install only when authorized.
  • On macOS, use agent-desktop permissions --guide and ask the user to grant Accessibility. Screenshots also need Screen Recording permission.
  • At first use, load both upstream guides rather than guessing command syntax:
agent-desktop skills get desktop
agent-desktop skills get platform

Work loop

  1. Identify the requested app/window with list-apps or list-windows as needed.
  2. Read agent-desktop snapshot --app "<App>" -i.
  3. Use current snapshot refs with click, set-value, type, or press, following the loaded guides. Quote refs in PowerShell.
  4. Re-snapshot after UI changes before choosing another ref. Use find, get, or is for targeted inspection; use mouse-click only when refs cannot address the target.

Tracing is off unless you pass --trace <path>; only pass it when the task needs a trace. Keep traces and screenshots out of repositories and avoid capturing credentials or unrelated private content.

Platform limits and approval

  • Default operation is background friendly. Use --headed only when needed: it moves the real cursor and can steal focus.
  • Windows type and right-click require headed mode. Windows/Linux headless key actions need the target focused; do not assume background targeting establishes focus.
  • Hyprland/Wayland pointer, drag, and window control are unsupported; report that limit rather than improvising another runtime.
  • The CLI has no built-in confirmation or allowlist. Before account writes, purchases, sends, or deletions, require explicit user approval for that exact action and target. Existing action-specific approval suffices.
  • Never use --force without explicit approval. Stop at permission/provider gates and report the blocker.
  • Report what the requested interaction returned; do not claim completion from a successful command alone.

Read the full file on GitHub · 40 lines

Changes

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.

  1. today First seen · 40 lines · 38 tokens per session scan A 5131334dbd0f

Subscribe to this mod's changes

agent-desktop is a skill published in the GitHub repository travisjneuman/.claude (106 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 565 once invoked, about $0.0002 per session on Opus 5.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-11-01.

Related

Other skills, from other repositories

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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…

microsoft/vscode · 72 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.

microsoft/vscode · 53 tokens