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
- 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.
Curated by Skill Harbor — @mitsuhiko's web-browser skill: a minimal CDP toolkit so an agent can drive a real Chrome — launch headless with an isolated fresh profile (or a copy of your own profile, never the live one), navigate, click, fill forms, evaluate JavaScript, take viewport or full-page screenshots, emulate mobile devices (iPhone/Pixel presets), dismiss EU cookie dialogs, and capture console, error and network activity as JSONL logs with a net-summary helper. Thoughtful safety boundaries: isolated profiles by default, headed mode only when a person must see or authenticate, pick-element requires a visible window, and the skill refuses to attach to your live Chrome session. Honest caveats: needs Node.js and a Chrome/Chromium install on the agent's machine; `--profile` copy mode loads your cookies — convenient for authenticated flows, keep session hygiene in mind; the SKILL.md frontmatter jokingly says "license: Stolen from Mario" — the repo's declared license is Apache-2.0. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
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://github.com/mitsuhiko/agent-stuff/blob/main/skills/web-browser/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 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.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.