← Search

Web browser automation via Chrome DevTools Protocol: headless Chrome control from scripts
Browser Automation 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit 0865c84
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: Node.js and Chrome or Chromium installed on the…

Web browser automation via Chrome DevTools Protocol: headless Chrome control from scripts

Headless Chrome with isolated or copied profiles, navigate/click/fill via CDP scripts, screenshots, device emulation, console+network JSONL logging, and cookie-dialog dismissal

At a glance
What
Headless Chrome with isolated or copied profiles, navigate/click/fill via CDP scripts, screenshots, device emulation, console+network JSONL logging, and cookie-dialog dismissal
Cost
Free
Needs
Node.js and Chrome or Chromium installed on the agent's machine — the scripts launch a real browser locally
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

Web browser automation is a free Muse skill for headless Chrome control from scripts via the Chrome DevTools Protocol. It covers isolated or copied profiles, navigate, click and fill actions, screenshots, device emulation and console plus network JSONL logging. It also dismisses cookie dialogs, making scripted browsing practical and observable.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 0865c84

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: Node.js and Chrome or Chromium installed on the agent's machine — the scripts launch a real browser locally Install "Web browser automation via Chrome DevTools Protocol: headless Chrome control from scripts" for me. It gives my agent @mitsuhiko's CDP toolkit: launch headless Chrome with isolated or copied profiles (scripts/start.js), navigate/click/fill/eval via scripts (nav.js, eval.js, pick.js), viewport and full-page screenshots, mobile device emulation presets, EU cookie-dialog dismissal, and JSONL console+error+network logging with a net-summary helper. Apache-2.0 licensed. Repository: https://raw.githubusercontent.com/mitsuhiko/agent-stuff/0865c849befd2021490679f96a8dee58c84ac857/skills/web-browser/SKILL.md Pinned version: install the code at commit 0865c849befd2021490679f96a8dee58c84ac857 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "web-browser". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. confirm Node.js and Chrome/Chromium are installed where the agent runs scripts; choose headless (default, isolated profile) vs --profile copy mode (loads my cookies — keep session hygiene in mind); stop the skill Chrome before switching modes). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 0865c84 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : registry.npmjs.org
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
0865c84 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: registry.npmjs.org
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.