Agent skill · software engineering · nexu-io
agent-browser
Browser automation CLI for AI agents. Use when the user needs to inspect, test, or automate browser behavior: navigating pages, filling forms, clicking buttons, taking screenshots, extracting page data, reading selected OpenDesign browser-tab context, testing web apps, dogfooding OpenDesign previews, QA, bug hunts, or reviewing app quality. Prefer local OpenDesign preview URLs unless the user explicitly asks for external browsing.
Why this skill is useful
Adds specific commands and workflows for browser automation that the AI wouldn't reliably generate on its own.
What it needs
Requires npm installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 84,236 stars on the source repository.
What this skill does
Agent Browser Use agent-browser for local OpenDesign preview validation: inspect rendered state, click/type when requested, and capture one screenshot when visual evidence matters. Keep the browser local-first unless the user explicitly asks for external browsing. When the run prompt contains selected workspace context, prefer the selected browser tab URL/title as the target. Treat user phrases like "this page", "the current browser", "right-side tab", "extract the logo", "get the palette", "take an element screenshot", or "check OG/a11y" as requests about that selected tab unless the user names another target. Requirements Verify the CLI before doing any browser work: If missing, stop and tell the user to install it: Do not replace the CLI with ad hoc browser scripts. Context Hygiene Never print full upstream guides into chat or tool output. Save them to temp files and extract only task-relevant lines: Use agent-browser skills get core --full only when needed, and redirect it to a temp file the same way. Browser Context Extraction For selected OpenDesign browser tabs and browser-use/browser-harness-style tasks, collect the smallest useful evidence first: 1. Confirm the target with agent-browser get title and agent-browser get url. 2. Capture agent-browser snapshot before any extraction or click. 3. For visual evidence, save a page screenshot and, when the core guide exposes an element-screenshot command, capture the specific element instead of a cropped full page. 4. For logos, fonts, colors, images, motion code, OG metadata, page structure, and accessibility checks, prefer DOM/CSS/accessibility evidence from the attached browser over guessing from the rendered screenshot alone. 5. If the selected OpenDesign context only provided a URL/title and no browser automation tool is attached, say that directly and do not invent page internals. Save extracted design evidence as compact notes or assets in the project when the user is building from the reference. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nexu-io/agent-browser