Orca is an application for running and coordinating multiple coding agents, giving each agent an isolated Git worktree while tracking their work in one place. Developers use it to run agents such as Codex, ClaudeCode, OpenCode, or Pi in parallel across desktop, mobile, local terminals, or remote servers.
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 stablyai/orca --skill computer-usegit clone --depth 1 https://github.com/stablyai/orcaWrote 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/stablyai/orca/computer-use)<a href="https://agentmods.dev/skills/stablyai/orca/computer-use"><img src="https://agentmods.dev/badge/skills/stablyai/orca/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/stablyai/orca/computer-use"><img src="https://agentmods.dev/badge/skills/stablyai/orca/computer-use.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00100 | $0.00517 |
| Opus 5.5 | $0.00040 | $0.00207 |
| Sonnet 5.5 | $0.00020 | $0.00103 |
| Haiku 4.5 | $0.00010 | $0.00052 |
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 23d 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.
Copies of this mod
4 near-identical copies found in the catalogue:
- computer-use — 100% identical, 57 lines differ
- computer-use — 100% identical, 57 lines differ
- computer-use — 100% identical, 0 lines differ
- computer-use — 100% identical, 0 lines differ
What it actually says
Computer Use
This discovery stub loads the version-matched guide from the Orca executable used for this session.
Resolve the CLI for this session
Choose the executable once and reuse it for every later command:
- If the
ORCA_CLI_COMMANDenvironment variable is set, use its value. Orca exports this for managed WSL sessions. - Otherwise, in a dev checkout whose session exposes
ORCA_DEV_REPO_ROOT, useorca-dev. - Otherwise, on Linux outside an Orca-managed terminal, use
orca-ide. Never run bareorcathere — outside Orca's terminals it normally resolves to the GNOME Orca screen reader (/usr/bin/orca) and starts speech on the user's machine. - Otherwise, use
orca.
Below, ORCA is a placeholder for the executable you resolved. Substitute it before
running anything; do not create a shell variable or run ORCA literally. This works the
same way in POSIX shells, PowerShell, and cmd.exe.
If the selected executable cannot run, report its exact error and stop. Do not fall through to another executable, which could silently target a different Orca build.
Load the version-matched guide before running Orca commands
ORCA skills get computer-use
Prefer --json. Use the selected executable's --help for commands or flags the guide does
not cover. If a command reports that Orca is not running, start it with ORCA open --json
and retry. If it fails with runtime_access_denied, your sandbox blocked the connection:
re-run it with escalated permissions, and do not run ORCA open or restart Orca. If
skills get is unknown, explain that updating Orca restores the guide; use --help for
read-only discovery and do not guess unsupported commands.
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.
- 23d ago Changed · +2 lines 2839933fd352
- 1mo ago Changed · +3 lines · +38 tokens per session 244b06656c84
- 1mo ago Changed · -31 lines · -37 tokens per session da1df6e6dab9
- 1mo ago Changed · -3 lines · -22 tokens per session a3fcca06875e
- 1mo ago First seen · 76 lines · 121 tokens per session scan A c4a11596b7c0
computer-use is a skill published in the GitHub repository stablyai/orca (94,483 stars, last pushed today), licensed MIT. It adds 100 tokens to every session and 517 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
verify
Drive an engine app headlessly in a pty, record a video of the whole verification, and open a summary page (video + timeline + checks) with pixel open.
browser
Open, navigate, screenshot, read, click, and type in web pages from an agent. Use when the user asks to open a URL, preview or verify a running web app, check a page's console, fill a form, click through a web flow, or automate anything in a browser, including "open localhost:3000", "screenshot the page", "what does…
core-agent-browser
Internal support skill for agent-browser CLI workflows used by rust-learner, docs-researcher, and crate-researcher. Use only when browser automation is explicitly required.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to inspect, test, or automate browser behavior: navigating pages, filling forms, clicking buttons, taking screenshots, extracting page data, testing web apps, dogfooding Open Design previews, QA, bug hunts, or reviewing app quality. Prefer local Open Design…
browser-use
Control the user's Chrome through the existing persistent Node REPL and the Qwen Browser SDK.
opencli-autofix
Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through collecting a trace artifact, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix. Works with any AI agent.