Agent skill

Browser Automation

A skill your agent uses when the agent must open a URL, fill a form, click through a flow, screenshot a page, or extract data from a live page.

Custom licenceAuto-check passedProductivity & Automation

Install Browser Automation

skills CLI

$ npx skills add coco-research/coco --skill browser-automation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install coco-research/coco browser-automation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/coco-research/coco.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/browser-automation .claude/skills/browser-automation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "browser-automation" agent skill from https://github.com/coco-research/coco/tree/main/skills/browser-automation into .claude/skills/browser-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-automation", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/coco-research/coco/tree/main/skills/browser-automation

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add coco-research/coco --skill browser-automation -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install coco-research/coco browser-automation --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/coco-research/coco.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/browser-automation .agents/skills/browser-automation && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "browser-automation" agent skill from https://github.com/coco-research/coco/tree/main/skills/browser-automation into .agents/skills/browser-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-automation", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add coco-research/coco --skill browser-automation -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install coco-research/coco browser-automation --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/coco-research/coco.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/browser-automation .cursor/skills/browser-automation && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "browser-automation" agent skill from https://github.com/coco-research/coco/tree/main/skills/browser-automation into .cursor/skills/browser-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-automation", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/coco-research/coco.git --path skills/browser-automation

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add coco-research/coco --skill browser-automation -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install coco-research/coco browser-automation --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/coco-research/coco.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/browser-automation .gemini/skills/browser-automation && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "browser-automation" agent skill from https://github.com/coco-research/coco/tree/main/skills/browser-automation into .gemini/skills/browser-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-automation", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install coco-research/coco browser-automation

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add coco-research/coco --skill browser-automation -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/coco-research/coco.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/browser-automation .github/skills/browser-automation && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "browser-automation" agent skill from https://github.com/coco-research/coco/tree/main/skills/browser-automation into .github/skills/browser-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-automation", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add coco-research/coco --skill browser-automation -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install coco-research/coco browser-automation --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/coco-research/coco.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/browser-automation .opencode/skills/browser-automation && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "browser-automation" agent skill from https://github.com/coco-research/coco/tree/main/skills/browser-automation into .opencode/skills/browser-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-automation", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: browser-automation
GitHub stars: 482
Token cost: ~2.3k tokens
SKILL.md length: 410 words
Files: 1
Skills in repo: 57
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: Custom licence

At a glance

A skill your agent uses when the agent must open a URL, fill a form, click through a flow, screenshot a page, or extract data from a live page.

Works in 4 steps: Navigate — Open a URL → Snapshot — Get @e refs for interactive… → Interact — Use refs to click, fill, select → …
The agent must open a URL
SKILL.md covers Core Workflow (Both Providers), Provider 1: agent-browser…, Provider 2: agentic-browser… and Common Patterns (Both Providers)
Calls jq, curl and npm; reaches site-a.com and site-b.com

What it does

Browser Automation is an agent skill from coco-research/coco. Use when the agent must open a URL, fill a form, click through a flow, screenshot a page, or extract data from a live page. Covers two providers (agent-browser local CLI, agentic-browser cloud) and the shared @e ref workflow.

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Productivity & Automation, covering Browser automation. The repository describes itself as: CoCo Super Intelligence is the orchestration layer that turns Claude Code, Cursor, or Codex into an engineering department: a routed advisory board, 226 skills, 386 commands…

When your agent uses it

The agent must open a URL
Click through a flow
Screenshot a page
Extract data from a live page

Example prompts

“/browser-automation”

Requirements

Node.js
Pre-approved tools (allowed-tools): Bash(agent-browser:*), Bash(infsh *)

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Navigate — Open a URL
Snapshot — Get @e refs for interactive elements
Interact — Use refs to click, fill, select
Re-snapshot — After navigation or DOM changes, get fresh refs

What it can do on your machine

Read from SKILL.md and the folder at commit 2ddb559. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Bash(agent-browser:*)
- Bash(infsh *)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- jq
- curl
- npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- site-a.com
- site-b.com
- cli.inference.sh
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Browser Automation loads about 2.3k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 410 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~61
When it runs · the whole SKILL.md, loaded when a task matches: ~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 410 words (~2,319 tokens).

“Browser automation for AI agents with two provider options. Both share the same core workflow: navigate, snapshot, interact using @e refs, re-snapshot after changes.”

— opening of SKILL.md by coco-research, Custom licence

name: browser-automation
allowed-tools: Bash(agent-browser:*), Bash(infsh *)
domain: engineering

Outline of SKILL.md

Browser Automation
Core Workflow (Both Providers)
Provider 1: agent-browser (Local CLI)
Quick Start
Essential Commands
Authentication with State Persistence
Parallel Sessions
Visual / Debugging
Local Files
iOS Simulator (Mobile Safari)
Semantic Locators (Alternative to Refs)
Provider 2: agentic-browser (Cloud via inference.sh)
Quick Start
Core Functions
Interact Actions
Full Example
Video Recording
Proxy Support
File Upload
JavaScript Execution
Common Patterns (Both Providers)
Form Submission
Data Extraction
Authentication Flow

Read the full SKILL.md on GitHub

Files

Just SKILL.md in skills/browser-automation of coco-research/coco.

Open the folder on GitHubat commit 2ddb559

Compare with similar skills

Browser Automation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Browser Automation compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Browser Automation this skillcoco-research/coco	482	—	~2.3k	Automated safety check: Pass	Custom licence	today
Agent Browserquran/quran.com-frontend-next	1.9k	42 repos	~3.3k	Automated safety check: Pass	None	5 mo ago
Dev-Browser CLI AutomationSawyerHood/dev-browser	6.7k	1 repos	~455	Automated safety check: Pass	MIT	1 mo ago
Agent Browsersuperagent-ai/grok-cli	3.5k	1 repos	~633	Automated safety check: Pass	MIT	3 mo ago
Browser Automationopenclaw/openclaw	392k	—	~2.9k	Automated safety check: Pass	MIT	today
Camoufox CLIBin-Huang/camoufox-cli	350	1 repos	~4.5k	Automated safety check: Pass	MIT	7 days ago

Similar skills

Agent Browser
quran/quran.com-frontend-next
Automates browser interactions for web testing, form filling, screenshots, and data extraction.
1.9k GitHub starsUsed in 42 repos~3.3k tokens
Productivity & AutomationAuto-check passed
Dev-Browser CLI Automation
SawyerHood/dev-browser
Browser automation with persistent named pages via the dev-browser CLI. Use when users ask to navigate websites, fill forms, take screenshots, extract web…
6.7k GitHub starsUsed in 1 repo~455 tokens
Productivity & AutomationAuto-check passed
Agent Browser
superagent-ai/grok-cli
Use the host-side agent-browser CLI for local browser smoke tests, screenshots, snapshots, and simple UI validation against forwarded localhost URLs.
3.5k GitHub starsUsed in 1 repo~633 tokens
Productivity & AutomationAuto-check passed
Browser Automation
openclaw/openclaw
A skill your agent uses when controlling web pages with the OpenClaw browser tool, especially multi-step flows, login checks, tab management, or recovery from stale refs/timeouts.
392k GitHub stars~2.9k tokensUpdated today
Productivity & AutomationAuto-check passed
Camoufox CLI
Bin-Huang/camoufox-cli
Anti-detect browser automation CLI & Skills for AI agents. An agent skill from Bin-Huang/camoufox-cli.
350 GitHub starsUsed in 1 repo~4.5k tokens
Productivity & AutomationAuto-check passed
Browser
VibiumDev/vibium
Automate browsers with the Vibium CLI. An agent skill from VibiumDev/vibium.
2.9k GitHub stars~4.8k tokensUpdated today
Productivity & AutomationAuto-check passed

Questions about Browser Automation

What does Browser Automation do?

A skill your agent uses when the agent must open a URL, fill a form, click through a flow, screenshot a page, or extract data from a live page. Browser Automation is an agent skill from coco-research/coco. Use when the agent must open a URL, fill a form, click through a flow, screenshot a page, or extract data from a live page.

When should I use Browser Automation?

Browser Automation fits situations like: the agent must open a URL; click through a flow; screenshot a page; extract data from a live page.

How do I install Browser Automation in Claude Code?

Run `npx skills add coco-research/coco --skill browser-automation -a claude-code`. Or copy the skill folder (skills/browser-automation in coco-research/coco) into .claude/skills/browser-automation in your project. Claude Code loads it when a task matches its description.

How do I install Browser Automation in Codex?

Run `npx skills add coco-research/coco --skill browser-automation -a codex`. Or copy the skill folder (skills/browser-automation in coco-research/coco) into .agents/skills/browser-automation in your project. Codex loads it when a task matches its description.

Can I use Browser Automation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add coco-research/coco --skill browser-automation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/browser-automation, .gemini/skills/browser-automation, .github/skills/browser-automation and .opencode/skills/browser-automation in your project.

What does Browser Automation need to run?

Going by SKILL.md and its folder, Browser Automation needs the command-line tools its instructions call (jq, curl and npm). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Bash(agent-browser:*), Bash(infsh *).

Does Browser Automation access the network?

SKILL.md names 3 domains. In commands or code: site-a.com, site-b.com and cli.inference.sh; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Browser Automation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Browser Automation use?

Browser Automation has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Browser Automation use?

About 2.3k tokens (SKILL.md is roughly 9.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Browser Automation?

Skills that share tags, products or a category with Browser Automation: Agent Browser (quran/quran.com-frontend-next, 1.9k stars), Dev-Browser CLI Automation (SawyerHood/dev-browser, 6.7k stars), Agent Browser (superagent-ai/grok-cli, 3.5k stars) and Browser Automation (openclaw/openclaw, 392k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Browser Automation?

coco-research (a GitHub user) maintains it in coco-research/coco, which has 482 GitHub stars. The repository holds 57 skills in this directory. The repository was last updated on October 8, 2026.

Source: coco-research/coco on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Browser Automation

Install Browser Automation

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Files

Compare with similar skills

Similar skills

Agent Browser

Dev-Browser CLI Automation

Agent Browser