Browser Automation · IN-DEPTH PROFILE

Agent Browser Skill

Browser automation built for repeatable agent workflows.

View listed source ↗Installation guide ↓Read the Browser Automation Top 5 guide ↗
Best for

QA and frontend engineers

What you get

Inspect pages + Automate interactions

Main limitation

The checked-in SKILL.md is a discovery stub; full instructions come from the installed CLI version.

First risk

Browser-side actions. The CLI can act in authenticated sessions and execute JavaScript. Use isolated profiles, scoped accounts, and domain allowlists.

EVIDENCE FRESHNESS

Three checks, kept separate

A recent source check is not a runtime test or security audit.

Upstream sourceChecked 2026-09-23

Pinned revision · d01253d9

Open pinned commit ↗
SkillSignal profileSource-grounded

Updated 2026-08-20

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

IN PLAIN ENGLISH

What it does—and when it fits

Agent Browser is Vercel's browser automation CLI Skill. The current upstream stub directs users to version-matched workflow content from the installed CLI, which provides persistent Chrome or Chromium sessions, accessibility-tree snapshots, element references, interactions, extraction, cookies, JavaScript execution, and remote-browser options.

This is aimed at QA and frontend engineers. Compare the examples below with your task, then review the limitations, permissions, and risks before installing.

What you get
  • Inspect pagesNavigate and capture compact accessibility snapshots for agent reasoning.
  • Automate interactionsClick, type, upload, and manage sequential steps in one persistent session.
  • Extract and scriptCollect page data or execute bounded browser-side JavaScript when required.
What makes it different
  • This profile is manually organized around the current upstream SKILL.md workflow.
  • The capability boundary remains explicitly tied to vercel-labs.
  • Core uses, limitations, and risks are separated for pre-install review.
Community signalskills.sh All-time: #6 · 952.0K installs

A GitHub issue asked for clearer use cases and validation examples because the README did not make the workflow obvious.

That feedback is a useful evaluation rule: a browser Skill should show the task, a minimal example, and what success looks like—not only list commands.GitHub issue #240 · vercel-labs/agent-browser ↗

INSTALL BY AGENT

Choose your Agent

Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.

Native

This Skill's current record explicitly names this Agent. Still inspect scripts, permissions, and external dependencies first.

Project install (recommended)
npx skills add https://github.com/vercel-labs/agent-browser --skill agent-browser --agent claude-code
Personal install
npx skills add https://github.com/vercel-labs/agent-browser --skill agent-browser --agent claude-code -g

Project install stays with this repository for team sharing. Personal install adds -g and works across repositories.

View install paths
Project path.claude/skills/agent-browser/
Personal path~/.claude/skills/agent-browser/
Official agent docs

Claude Code discovers custom Skill folders automatically at project or personal scope.

View path evidence ↗

TYPICAL WORKFLOW

A practical workflow

01

Inspect pages

Navigate and capture compact accessibility snapshots for agent reasoning.

02

Automate interactions

Click, type, upload, and manage sequential steps in one persistent session.

03

Extract and script

Collect page data or execute bounded browser-side JavaScript when required.

THE TRADEOFFS

Advantages and tradeoffs

Notable strengths

  1. This profile is manually organized around the current upstream SKILL.md workflow.
  2. The capability boundary remains explicitly tied to vercel-labs.
  3. Core uses, limitations, and risks are separated for pre-install review.

Limitations

  1. The checked-in SKILL.md is a discovery stub; full instructions come from the installed CLI version.
  2. Browser flows remain sensitive to site changes, bot defenses, consent dialogs, and session state.

COMPARE THE TRADEOFF

Consider these close alternatives

These are deterministic nearby candidates, not paid placements or a universal ranking. Open the full profile before choosing.

01

Same job family · native to Codex + Claude Code

chrome-devtools

Automate, debug, and profile web pages through Chrome DevTools MCP.
Tradeoff to check
Detailed package files are not fully catalogued.
First risk
Review before install · Medium
Source state
Pinned · 1f564408
Open chrome-devtools profile ↗
02

Same job family · native to Claude Code + Codex

browser-use

Structured browser tasks with navigation and extraction patterns.
Tradeoff to check
Detailed package files are not fully catalogued.
First risk
Review before install · Medium
Source state
Editorial source
Open browser-use profile ↗
03

Same job family · native to Codex + Claude Code

playwright-workflows

Repeatable end-to-end browser testing and inspection workflows.
Tradeoff to check
Detailed package files are not fully catalogued.
First risk
Review before install · Medium
Source state
Editorial source
Open playwright-workflows profile ↗
Compare more in the directory →

BEST FIT

Who it is for

→

QA and frontend engineers

→

Agents automating controlled browser workflows

BEFORE YOU USE IT

Risks to review before use

High

Browser-side actions

The CLI can act in authenticated sessions and execute JavaScript. Use isolated profiles, scoped accounts, and domain allowlists.

Medium

Upstream instruction drift

Behavior can change with upstream updates. Record the commit used for important workflows and review updates before adoption.

SECURITY

What the permission profile means

  • Declared access remains governed by the current upstream SKILL.md and runtime requests.
  • Treat repository files, web content, and tool output as untrusted input.
  • SkillSignal has not independently executed or security-audited this package; external skills.sh labels are not SkillSignal certification.

Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.

COMMON QUESTIONS

Agent Browser Skill FAQ

What is the Agent Browser Skill?

Browser automation built for repeatable agent workflows. Agent Browser is Vercel's browser automation CLI Skill. The current upstream stub directs users to version-matched workflow content from the installed CLI, which provides persistent Chrome or Chromium sessions, accessibility-tree snapshots, element references, interactions, extraction, cookies, JavaScript execution, and remote-browser options.

How do I install the Agent Browser Skill?

Open and review the listed source, choose the project or personal path for your Agent, then verify the first run in a controlled project. Open the listed skills.sh page and upstream repository; verify the current SKILL.md.

Is the Agent Browser Skill safe to use?

SkillSignal checked the source on 2026-09-23, but that is not a runtime test or security certification. Review the “Browser-side actions” risk first and begin with the least access required.

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream Skill instructionsSource-linked

TAGS

browserautomationcdp

Manually expanded from the current upstream SKILL.md and linked source at vercel-labs, checked 2026-08-19. This is an original summary, not an execution result or security certification.