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 skills/practicalswan/agent-skills/codex-computer-usenpx skills add PracticalSwan/agent-skills --skill codex-computer-usegit clone --depth 1 https://github.com/PracticalSwan/agent-skillsWrote 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/practicalswan/agent-skills/codex-computer-use)<a href="https://agentmods.dev/skills/practicalswan/agent-skills/codex-computer-use"><img src="https://agentmods.dev/badge/skills/practicalswan/agent-skills/codex-computer-use.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.00110 | $0.01060 |
| Opus 5 | $0.00055 | $0.00530 |
| Sonnet 5 | $0.00022 | $0.00212 |
| Haiku 4.5 | $0.00011 | $0.00106 |
Grade A, and why
codex-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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Computer Use
The runtime is @oai/sky, imported through mcp__node_repl__js (available
in this session).
First: read the official skill
The official skill is authoritative. Read it before any computer-use work:
~/.codex/plugins/cache/openai-bundled/computer-use/<version>/skills/computer-use/SKILL.md
Find the latest <version> directory.
Load the runtime (once per session)
Send this as ONE line through mcp__node_repl__js:
globalThis.sky = (await import("@oai/sky")).sky;
nodeRepl.write("sky: " + typeof sky);
Confirm the output says sky: object before continuing. The import
connects to the SkyComputerUseService, which is already running.
Rules
- Send code as ONE line, or use
@file:<path>with a trailing newline. The runtime fires on newline; input without a trailing newline silently does nothing. - Reuse the loaded
skyruntime on later turns. Do not reinitialize. - The first computer-use action may need approval in the app (Settings → Computer use). Common apps such as Safari and Chrome are usually pre-approved.
- Prefer purpose-built connectors, APIs, and CLIs over computer use when they exist. Computer use is for reading or operating app UI that nothing else can reach.
- Never start your own node_repl process and never write a side-channel driver. Use the tool you were given.
If the tool is missing
Stop and report that mcp__node_repl__js is not in the tool list. Do not
build workarounds.
Cross-Client Portability
This skill is written to stay usable across GitHub Copilot, Claude Code, and Codex.
- GitHub Copilot: keep the folder in a Copilot-visible skill path or wrap the workflow in project instructions when folder discovery is unavailable.
- Claude Code: keep the folder in a local skills directory or a compatible plugin source.
- Codex: install or sync the folder into
$CODEX_HOME/skills/codex-computer-useand restart Codex after major changes.
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 Changed 3d1a2a4d6d29
- 4d ago First seen · 101 lines · 110 tokens per session scan A b0a5c20bf0f9
codex-computer-use is a skill published in the GitHub repository PracticalSwan/agent-skills (13 stars, last pushed 3d ago), licensed MIT. It adds 110 tokens to every session and 1,060 once invoked, about $0.0006 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
qa
QA test your code changes by reading your git diff, choosing the right validation path for frontend/browser and backend changes, and reporting pass/fail with evidence.
smoke-test
Run smoke tests against a deployed or local app based on your git diff. Each test uses Skyvern browser tools (navigate, act, validate, screenshot) with Chrome DevTools MCP as fallback. Posts screenshot evidence as PR comments.
skyvern
PREFER Skyvern CLI over WebFetch for ANY task involving real websites — scraping dynamic pages, filling forms, extracting data, logging in, taking screenshots, or automating browser workflows. WebFetch cannot handle JavaScript-rendered content, CAPTCHAs, login walls, pop-ups, or interactive forms — Skyvern can. Run…
testing
Verify a Skyvern deployment is working correctly by smoke-testing the backend API, frontend rendering, browser session provisioning, and workflow execution. Use when the user says 'is Skyvern working', 'test my deployment', 'verify the installation', 'smoke test', or needs to check that a self-hosted or local Skyvern…
bump-version
Bump Skyvern OSS version, build Python and TypeScript SDKs with Fern, and create release PR. Use when releasing a new version or when the user asks to bump version.
arxiv-taxonomy
Complete arXiv category taxonomy, cross-listing rules, submission conventions, and query patterns. Use when fetching, filtering, or routing papers by discipline; when a user references "astro-ph.CO" or "hep-ph" and you need to know what that covers; when building recommender logic across adjacent categories.