Individual skill

control-browser

Use when opening, navigating, inspecting, testing, clicking, typing, filling, screenshotting, or verifying web pages and local HTTP targets (localhost, 127.0.0.1, ::1) inside ZCode, including browser/web-UI automation, rendered-page scraping, frontend checks, and visible page-state reading. Prefer this over Computer Use for anything that stays inside a web page, unless the user explicitly asks for Computer Use. Main agent only.

GLM/skills/control-browser/SKILL.md

Read pinned source

Source commit a2d33761e49b98f6ec1b48f12143264eb9b4ff4f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 10, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
71,199
Repository last updated
Nov 10, 2026
License
CC0-1.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Browser automation (agent.browsers)

Use this skill for browser / web-UI tasks: opening and navigating pages, inspecting or reading rendered content, testing local apps, clicking, typing, filling, taking screenshots, and verifying visible page state.

If this skill is available in the session, treat it as required reading before browser work. Follow it before saying the browser is unavailable and before falling back to `bash` (curl/open), `webfetch`, or any other tool for a browser task.

## How it works

The browser registry is driven from the Node REPL MCP `js` tool. In this environment its callable id normally appears as `mcp__node_repl__js`. The MCP frontend is shared for a workspace, but every `js` call runs in a fresh JavaScript kernel, so variables, imports, module cache, `browser`, and `tab` bindings do not persist. Persistent BrowserControl tabs are the continuity boundary and must be recovered from current tab facts.

## Bootstrap every JavaScript call

The `browser-client` module is the browser entry point and is available at `scripts/browser-client.mjs` under this plugin's root. Resolve that root only from `process.env.ZCODE_PLUGIN_ROOT` (with `CLAUDE_PLUGIN_ROOT` as a compatibility fallback), then convert the joined path with `pathToFileURL`. Never derive the plugin root from this skill's base directory or leave a synthetic root placeholder for the model to resolve. If the host root is unavailable or the resolved module cannot be imported, stop and report the exact setup error.
Back to top