browser-harness
Direct browser control via CDP. Use when the user wants to automate, scrape, test, or interact with web pages. Connects to the user's already-running Chrome.
Install
With your agent
Install OMGSkills skill "davidondrej/skills:browser-harness" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/davidondrej/skills /tmp/skills && ln -s /tmp/skills/skills/research-and-web/browser-harness ~/.claude/skills/browser-harnessFrom README
browser-harness Direct browser control via CDP. For task-specific edits, use agent-workspace/agenthelpers.py. For , , or connection problems, read .md. Routing check first: if the task needs no interaction (no clicks, logins, or forms) and you just want page content, use DeepAPI POST /v1/scrape/website instead of driving a browser — see the deepapi skill. Use browser-harness when the task needs a real browser: interaction, JS-heavy flows, logged-in sessions, or visual verification. Domain skills (community-contributed per-site playbooks under agent-workspace/domain-skills/) are off by default. Set BHDOMAINSKILLS=1 to enable them; see the bottom section. If BHDOMAINSKILLS=1 and the task is site-specific, read every file in the matching agent-workspace/domain-skills/ / directory before inventing an approach. Invoke as browser-harness — it's on $PATH. No cd, no uv run. First navigation is newtab(url), not gotourl(url) — goto runs in the user's active tab and clobbers their work.
More from this repo
anti-sleep
Keep a Mac awake for a set duration or while a process runs.
adr-verbatim
Record concise ADRs that preserve the user's decisions without conversational noise.
ask-then-build
Clarify a feature, change, or refactor through questions, then write a build prompt for another agent.