browser

Automates the Codex in-app browser for navigating, inspecting, and testing web pages.

Updated Sep 19, 2026
One-click install
npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill browser-ab0umar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser
Source: https://github.com/Ab0umar/selrs.cc.BU/tree/main/.codex/plugins/cache/openai-bundled/browser/0.1.0-alpha2/skills/browser
Command: npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill browser-ab0umar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Manually verifying local development pages and web apps is slow and repetitive. This Skill lets the AI open, navigate, click, type, screenshot, and inspect pages directly in the Codex in-app browser, so you can test localhost apps and verify UI behavior without leaving your workflow. ## Core Features & Use Cases - In-App Browser Automation: Control the Codex iab browser through a Node REPL runtime using Playwright locators, DOM snapshots, and screenshots. - Local Development Testing: Open localhost, 127.0.0.1, ::1, or file:// targets, reload after code changes, and verify UI state with fresh snapshots. - Safe Interaction Policy: Built-in confirmation rules for sensitive actions like form submissions, purchases, deletions, and logins. - Use Case: Ask the AI to open localhost:3000, log in to your app, click through the checkout flow, and return screenshots confirming each step works. ## Quick Start Ask the AI to open localhost:3000 in the in-app browser and verify that the login page loads correctly.

Frequently Asked Questions about browser

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test a localhost app with browser automation?▼

Set up the browser runtime via the Node REPL js tool, acquire the iab browser, and navigate a tab to your localhost URL. After code changes, call tab.reload() and take a fresh DOM snapshot or screenshot before verifying the UI.

How to click elements reliably with Playwright locators?▼

Take a fresh domSnapshot(), build a locator from stable attributes like data-testid or href, and call count() to confirm it resolves to exactly one element before clicking. Never retry a failing locator without a new snapshot.

Can I use external Playwright or Computer Use tools instead?▼

No. Only the Node REPL js tool with the browser-client runtime can control the in-app browser. External MCP browser tools, standalone Playwright servers, and Computer Use are not supported for this surface.

Why does my Playwright locator fail with a strict mode error?▼

A strict mode violation means the locator matches multiple elements. Take a fresh domSnapshot(), scope the locator to the correct container, or switch to a stronger attribute instead of using .first() as a shortcut.

What actions require user confirmation in browser automation?▼

Deleting data, submitting forms, sending messages, financial transactions, logins without prior approval, CAPTCHAs, and medical actions always require confirmation. Reading pages and ordinary navigation do not need confirmation.