Taizi Agent Browser

A fast Rust-based headless browser automation CLI with Node.js fallback that enables AI agents to navigate, click, type, and snapshot pages via structured co...

MIT-0 · Free to use, modify, and redistribute. No attribution required.

⭐ 0 · 22 · 1 current installs · 1 all-time installs

by@fresh3

fork of @TheSethRose/agent-browser (based on 0.2.0)

MIT-0

Security Scan

VirusTotal

Suspicious

View report →

OpenClaw

Suspicious

medium confidence

Purpose & Capability

The SKILL.md documents a Node-based CLI for browser automation which reasonably requires node/npm. However there are several mismatches: the registry metadata names this skill 'taizi-agent-browser' while the included _meta.json and SKILL.md refer to 'agent-browser' and a different ownerId/version; source/homepage are marked unknown/none. The description also mentions a Rust binary with Node fallback but the instructions only show installing an npm package or building from a GitHub repo — this ambiguous provenance and metadata mismatch is unexpected for a well-scoped wrapper.

ℹ

Instruction Scope

The SKILL.md confines runtime behavior to invoking the agent-browser CLI (navigate, snapshot, click, screenshot, etc.), which aligns with the stated purpose. It does instruct global npm installation and running 'agent-browser install' which may pull/execute additional artifacts. The allowed-tools entry (Bash(agent-browser:*)) means the agent will run that CLI directly; this is expected but gives the agent ability to execute arbitrary commands supported by that CLI. The instructions themselves do not ask to read unrelated local files or env vars.

Install Mechanism

There is no formal install spec — it's an instruction-only skill that tells users to run 'npm install -g agent-browser' or to clone a GitHub repo. That is a user action that will fetch and run third-party code outside the skill bundle. Because the package/package source is not verified here (no homepage, source unknown, and internal _meta.json disagrees with registry metadata), installing the npm package could introduce arbitrary native or JS code. The 'From Source' instructions point at a GitHub path but ownership/version inconsistencies reduce confidence.

✓

Credentials

Declared requirements are limited to node and npm binaries; no environment variables, credentials, or config paths are requested by the skill itself. That is proportionate to a CLI wrapper that runs a Node-based tool.

✓

Persistence & Privilege

always is false and the skill does not request persistent system-wide changes in its bundle. The skill allows the agent to invoke the CLI autonomously (disable-model-invocation=false) which is normal for skills. No indications the skill writes or modifies other skills or global agent settings were found.

Scan Findings in Context

[no-regex-findings] expected: The static regex scanner had nothing to analyze because this is an instruction-only skill with no code files. That absence is not evidence of safety — the SKILL.md instructs installing a package from npm or cloning a GitHub repo which the scanner could not fetch or inspect.

What to consider before installing

This skill appears to be a wrapper for an external npm CLI (agent-browser). Before installing or using it, verify the upstream package and repository: 1) Look up the 'agent-browser' package on the npm registry and confirm the package name, maintainer, and recent versions match the skill's documentation. 2) Inspect the package contents (npm pack, unpack locally) or review the GitHub repository code to ensure there are no post-install scripts or downloads from unknown URLs, native addons, or unaudited binaries. 3) Avoid global installs on sensitive machines; test inside an isolated container or VM. 4) Because a headless browser can access arbitrary websites and persist cookies/storage, avoid running it with credentials or against sensitive sites until you're comfortable with the package provenance. 5) The mismatched metadata (different ownerId/slug/version between registry metadata and _meta.json) is suspicious — if you cannot reconcile the source and maintainer, prefer not to install. If you want help, provide the exact npm package page or repository URL and I can re-evaluate with that provenance.

Like a lobster shell, security has layers — review code before you run it.

Current versionv1.0.0

Download zip

latestvk979fnhz0nt4fehg0hfte5w1z9830pqr

License

MIT-0

Free to use, modify, and redistribute. No attribution required.

Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

🌐 Clawdis

Binsnode, npm

SKILL.md

Browser Automation with agent-browser

Installation

npm recommended

npm install -g agent-browser
agent-browser install
agent-browser install --with-deps

From Source

git clone https://github.com/vercel-labs/agent-browser
cd agent-browser
pnpm install
pnpm build
agent-browser install

Quick start

agent-browser open <url>        # Navigate to page
agent-browser snapshot -i       # Get interactive elements with refs
agent-browser click @e1         # Click element by ref
agent-browser fill @e2 "text"   # Fill input by ref
agent-browser close             # Close browser

Core workflow

Navigate: agent-browser open <url>
Snapshot: agent-browser snapshot -i (returns elements with refs like @e1, @e2)
Interact using refs from the snapshot
Re-snapshot after navigation or significant DOM changes

Commands

Navigation

agent-browser open <url>      # Navigate to URL
agent-browser back            # Go back
agent-browser forward         # Go forward
agent-browser reload          # Reload page
agent-browser close           # Close browser

Snapshot (page analysis)

agent-browser snapshot            # Full accessibility tree
agent-browser snapshot -i         # Interactive elements only (recommended)
agent-browser snapshot -c         # Compact output
agent-browser snapshot -d 3       # Limit depth to 3
agent-browser snapshot -s "#main" # Scope to CSS selector

Interactions (use @refs from snapshot)

agent-browser click @e1           # Click
agent-browser dblclick @e1        # Double-click
agent-browser focus @e1           # Focus element
agent-browser fill @e2 "text"     # Clear and type
agent-browser type @e2 "text"     # Type without clearing
agent-browser press Enter         # Press key
agent-browser press Control+a     # Key combination
agent-browser keydown Shift       # Hold key down
agent-browser keyup Shift         # Release key
agent-browser hover @e1           # Hover
agent-browser check @e1           # Check checkbox
agent-browser uncheck @e1         # Uncheck checkbox
agent-browser select @e1 "value"  # Select dropdown
agent-browser scroll down 500     # Scroll page
agent-browser scrollintoview @e1  # Scroll element into view
agent-browser drag @e1 @e2        # Drag and drop
agent-browser upload @e1 file.pdf # Upload files

Get information

agent-browser get text @e1        # Get element text
agent-browser get html @e1        # Get innerHTML
agent-browser get value @e1       # Get input value
agent-browser get attr @e1 href   # Get attribute
agent-browser get title           # Get page title
agent-browser get url             # Get current URL
agent-browser get count ".item"   # Count matching elements
agent-browser get box @e1         # Get bounding box

Check state

agent-browser is visible @e1      # Check if visible
agent-browser is enabled @e1      # Check if enabled
agent-browser is checked @e1      # Check if checked

Screenshots & PDF

agent-browser screenshot          # Screenshot to stdout
agent-browser screenshot path.png # Save to file
agent-browser screenshot --full   # Full page
agent-browser pdf output.pdf      # Save as PDF

Video recording

agent-browser record start ./demo.webm    # Start recording (uses current URL + state)
agent-browser click @e1                   # Perform actions
agent-browser record stop                 # Stop and save video
agent-browser record restart ./take2.webm # Stop current + start new recording

Recording creates a fresh context but preserves cookies/storage from your session. If no URL is provided, it automatically returns to your current page. For smooth demos, explore first, then start recording.

Wait

agent-browser wait @e1                     # Wait for element
agent-browser wait 2000                    # Wait milliseconds
agent-browser wait --text "Success"        # Wait for text
agent-browser wait --url "/dashboard"    # Wait for URL pattern
agent-browser wait --load networkidle      # Wait for network idle
agent-browser wait --fn "window.ready"     # Wait for JS condition

Mouse control

agent-browser mouse move 100 200      # Move mouse
agent-browser mouse down left         # Press button
agent-browser mouse up left           # Release button
agent-browser mouse wheel 100         # Scroll wheel

Semantic locators (alternative to refs)

agent-browser find role button click --name "Submit"
agent-browser find text "Sign In" click
agent-browser find label "Email" fill "user@test.com"
agent-browser find first ".item" click
agent-browser find nth 2 "a" text

Browser settings

agent-browser set viewport 1920 1080      # Set viewport size
agent-browser set device "iPhone 14"      # Emulate device
agent-browser set geo 37.7749 -122.4194   # Set geolocation
agent-browser set offline on              # Toggle offline mode
agent-browser set headers '{"X-Key":"v"}' # Extra HTTP headers
agent-browser set credentials user pass   # HTTP basic auth
agent-browser set media dark              # Emulate color scheme

Cookies & Storage

agent-browser cookies                     # Get all cookies
agent-browser cookies set name value      # Set cookie
agent-browser cookies clear               # Clear cookies
agent-browser storage local               # Get all localStorage
agent-browser storage local key           # Get specific key
agent-browser storage local set k v       # Set value
agent-browser storage local clear         # Clear all

Network

agent-browser network route <url>              # Intercept requests
agent-browser network route <url> --abort      # Block requests
agent-browser network route <url> --body '{}'  # Mock response
agent-browser network unroute [url]            # Remove routes
agent-browser network requests                 # View tracked requests
agent-browser network requests --filter api    # Filter requests

Tabs & Windows

agent-browser tab                 # List tabs
agent-browser tab new [url]       # New tab
agent-browser tab 2               # Switch to tab
agent-browser tab close           # Close tab
agent-browser window new          # New window

Frames

agent-browser frame "#iframe"     # Switch to iframe
agent-browser frame main          # Back to main frame

Dialogs

agent-browser dialog accept [text]  # Accept dialog
agent-browser dialog dismiss        # Dismiss dialog

JavaScript

agent-browser eval "document.title"   # Run JavaScript

State management

agent-browser state save auth.json    # Save session state
agent-browser state load auth.json    # Load saved state

Example: Form submission

agent-browser open https://example.com/form
agent-browser snapshot -i
# Output shows: textbox "Email" [ref=e1], textbox "Password" [ref=e2], button "Submit" [ref=e3]

agent-browser fill @e1 "user@example.com"
agent-browser fill @e2 "password123"
agent-browser click @e3
agent-browser wait --load networkidle
agent-browser snapshot -i  # Check result

Example: Authentication with saved state

# Login once
agent-browser open https://app.example.com/login
agent-browser snapshot -i
agent-browser fill @e1 "username"
agent-browser fill @e2 "password"
agent-browser click @e3
agent-browser wait --url "/dashboard"
agent-browser state save auth.json

# Later sessions: load saved state
agent-browser state load auth.json
agent-browser open https://app.example.com/dashboard

Sessions (parallel browsers)

agent-browser --session test1 open site-a.com
agent-browser --session test2 open site-b.com
agent-browser session list

JSON output (for parsing)

Add --json for machine-readable output:

agent-browser snapshot -i --json
agent-browser get text @e1 --json

Debugging

agent-browser open example.com --headed              # Show browser window
agent-browser console                                # View console messages
agent-browser console --clear                        # Clear console
agent-browser errors                                 # View page errors
agent-browser errors --clear                         # Clear errors
agent-browser highlight @e1                          # Highlight element
agent-browser trace start                            # Start recording trace
agent-browser trace stop trace.zip                   # Stop and save trace
agent-browser record start ./debug.webm              # Record from current page
agent-browser record stop                            # Save recording
agent-browser --cdp 9222 snapshot                    # Connect via CDP

Troubleshooting

If the command is not found on Linux ARM64, use the full path in the bin folder.
If an element is not found, use snapshot to find the correct ref.
If the page is not loaded, add a wait command after navigation.
Use --headed to see the browser window for debugging.

Options

--session <name> uses an isolated session.
--json provides JSON output.
--full takes a full page screenshot.
--headed shows the browser window.
--timeout sets the command timeout in milliseconds.
--cdp <port> connects via Chrome DevTools Protocol.

Notes

Refs are stable per page load but change on navigation.
Always snapshot after navigation to get new refs.
Use fill instead of type for input fields to ensure existing text is cleared.

Reporting Issues

Skill issues: Open an issue at https://github.com/TheSethRose/Agent-Browser-CLI
agent-browser CLI issues: Open an issue at https://github.com/vercel-labs/agent-browser

Files

3 total

Select a file

Select a file to preview.

Comments

Loading comments…