Agent skill

Browser Control with Omowright

by code-yeongyu in code-yeongyu/oh-my-openagent

Drives a real browser through the omowright library, either the user's own signed-in browser or a separate browser the code launches, for forms, QA, screenshots and scraping.

Custom licenceAuto-check passedProductivity & Automation

Install Browser Control with Omowright

skills CLI
$ npx skills add code-yeongyu/oh-my-openagent --skill browser -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install code-yeongyu/oh-my-openagent browser --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/shared-skills/skills/browser .claude/skills/browser && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
browser
GitHub stars
70k
Token cost
~2.2k tokens
SKILL.md length
972 words
Files
16 (incl. scripts, references)
Skills in repo
44
Repo updated
First seen
Licence
Custom licence

At a glance

Drives a real browser through the omowright library, either the user's own signed-in browser or a separate browser the code launches, for forms, QA, screenshots and scraping.

  • Works in 2 steps: which engine this session is allowed to… → load omowright and prove the stack
  • Filling in a form or clicking through a site you are already signed into
  • SKILL.md covers Step 0 — which engine this…, Step 1 — load omowright and…, The loop (attached) and When a human is the only way…, plus 2 more sections
  • Runs JavaScript scripts from its folder; calls node

What it does

The skill ships with omowright and has two engines. The attached engine uses the user's own browser, with its logins and open tabs, and is the default: it suits forms, click-throughs, screenshots, web QA and extension popups, and a human is one call away when a login, CAPTCHA or one-time code appears. The owned engine is a browser the code launches itself, for throwaway profiles, network interception, QA flight traces, coordinate control, headless runs and scraping targets that score bots. For plain text from a URL or a blocked fetch it points to another skill instead.

When the `OMO_BROWSER_ENGINE` variable is set, it decides which engine the session may use: `connected` allows only the user's browser and stops with a relayed error if it is not connected, `builtin` uses the app's own browser tools, and `none` means no browser work. Under a set engine the library is guarded, so other engines are refused and the agent does not look for a way around that. In the connected mode the app asks you before any click or script that sends, posts, pays, orders, subscribes or deletes, and a refusal or a Stop is reported, never retried. Scripts for install, a doctor check and an engine guard are bundled, with references for commands, remote use and a 1Password recipe.

When your agent uses it

  • Filling in a form or clicking through a site you are already signed into
  • Taking screenshots or running web QA on a JavaScript-rendered page
  • Capturing network traffic or a QA trace in a browser the agent owns
  • Handing a login, CAPTCHA or one-time code step to the user

Example prompts

  • “Open my signed-in dashboard in the browser and screenshot the billing page.”
  • “Fill in the expense form in my open tab, but ask me before submitting.”
  • “Launch a clean browser, capture the network requests on this page and give me a QA trace.”

Requirements

  • Node.js, to run the bundled `.mjs` setup scripts
  • A browser connected through BrowserSkill, for the attached engine

Workflow steps

2 steps, taken from the step headings in SKILL.md.

  1. which engine this session is allowed to use
  2. load omowright and prove the stack

What it can do on your machine

Read from SKILL.md and the folder at commit cbd7dd2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 4 files in scripts/ (JavaScript), which the agent can run.

    Shell commands in SKILL.md call:

    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Browser Control with Omowright loads about 2.2k tokens when it runs, and up to ~9.4k if it reads all its reference files. Until then it costs about 105 tokens; SKILL.md has 972 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~105
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~9.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 972 words (~2,196 tokens).

“One library, two engines. omowright ships inside this skill; choose the engine before you act:”

— opening of SKILL.md by code-yeongyu, Custom licence
name
browser

Read the full SKILL.md on GitHub

Files

SKILL.md and 15 other files (scripts, references) in packages/shared-skills/skills/browser of code-yeongyu/oh-my-openagent.

  • SKILL.md
  • .gitignore
  • .npmignore
  • ATTRIBUTION.md
  • references/commands.md
  • references/install.md
  • references/owned-engine/README.md
  • references/owned-engine/frames-and-humans.md
  • references/owned-engine/ladder.md
  • references/owned-engine/network.md
  • references/recipes/1password.md
  • references/remote.md
  • scripts/browser-doctor.mjs
  • scripts/browser-engine-guard.mjs
  • scripts/browser-install.mjs
  • scripts/omowright.mjs

Open the folder on GitHubat commit cbd7dd2

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in code-yeongyu/oh-my-openagent, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Browser Control with Omowright next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Browser Control with Omowright compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Browser Control with Omowright this skillcode-yeongyu/oh-my-openagent70k—~2.2kAutomated safety check: PassCustom licence
Dev Browser AutomationMemTensor/MemOS12k3 repos~1.7kAutomated safety check: PassApache-2.0
Core Guide for agent-browservercel-labs/agent-browser44k4 repos~9.5kAutomated safety check: PassApache-2.0
Agent Browsernanocoai/nanoclaw31k3 repos~1.6kAutomated safety check: PassMIT
Playwright Bowserdisler/bowser265—~1.1kAutomated safety check: NotesNone
Browser Automationynulihao/AgentSkillOS617—~2.2kAutomated safety check: PassNone

Similar skills

  • Dev Browser Automation

    MemTensor/MemOS

    Automates a real browser through short TypeScript scripts that keep page state between runs, for navigating, filling forms, taking screenshots and extracting data.

    12k GitHub starsUsed in 3 repos~1.7k tokens
    Productivity & AutomationAuto-check passed
  • Core Guide for agent-browser

    vercel-labs/agent-browser

    Official

    Core usage guide for the agent-browser CLI: the snapshot-and-ref workflow for navigating, clicking, filling forms, extracting data and running parallel sessions.

    44k GitHub starsUsed in 4 repos~9.5k tokens
    Productivity & AutomationAuto-check passed
  • Agent Browser

    nanocoai/nanoclaw

    Drives a web browser from the shell with the agent-browser CLI: open pages, read an element snapshot, click and fill by reference, grab text and screenshots.

    31k GitHub starsUsed in 3 repos~1.6k tokens
    Productivity & AutomationAuto-check passed
  • Playwright Bowser

    disler/bowser

    Headless browser automation using Playwright CLI. An agent skill from disler/bowser.

    265 GitHub stars~1.1k tokensUpdated 7 mo ago
    Productivity & AutomationAuto-check: notes
  • Browser Automation

    ynulihao/AgentSkillOS

    Non-testing browser automation - web scraping, form filling, screenshot capture, PDF generation, workflow automation.

    617 GitHub stars~2.2k tokensUpdated 7 mo ago
    Productivity & AutomationAuto-check passed
  • Browser Use

    aiskillstore/marketplace

    Browser automation using Playwright MCP. An agent skill from aiskillstore/marketplace.

    430 GitHub stars~1.1k tokensUpdated today
    Productivity & AutomationAuto-check passed

More from code-yeongyu/oh-my-openagent

All 44 skills in this repo
  • ast-grep Structural Search

    code-yeongyu/oh-my-openagent

    Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.

    70k GitHub stars~3.3k tokensUpdated today
    Auto-check passed
  • Codex Plugin QA

    code-yeongyu/oh-my-openagent

    Tests the omo Codex plugin in an isolated CODEX_HOME with a local mock model, proving hooks fired through app-server notifications without touching ~/.codex.

    70k GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Coding Agent Session Finder

    code-yeongyu/oh-my-openagent

    Finds, reads and reconstructs past coding-agent sessions across Codex, Claude, OpenCode, Senpi and many other local agent logs.

    70k GitHub stars~2.8k tokensUpdated today
    Auto-check passed
  • LSP Setup

    code-yeongyu/oh-my-openagent

    Detects which languages a project uses, installs the matching language server, writes its config and checks it with a real call so diagnostics and go-to-definition work.

    70k GitHub stars~1.4k tokensUpdated today
    Auto-check: notes
  • OpenCode QA Toolkit

    code-yeongyu/oh-my-openagent

    Tests the opencode coding agent itself: its CLI, server, plugin hooks and events, the terminal UI under tmux, and its SQLite session database, using tested helper scripts.

    70k GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • ULW Plan Workflow

    code-yeongyu/oh-my-openagent

    Explore-first planning that turns a vague or large request into one decision-complete work plan, written only after your approval and executed by a separate worker.

    70k GitHub stars~3.9k tokensUpdated today
    Auto-check passed

Questions about Browser Control with Omowright

What does Browser Control with Omowright do?

Drives a real browser through the omowright library, either the user's own signed-in browser or a separate browser the code launches, for forms, QA, screenshots and scraping. The skill ships with omowright and has two engines. The attached engine uses the user's own browser, with its logins and open tabs, and is the default: it suits forms, click-throughs, screenshots, web QA and extension popups, and a human is one call away when a login, CAPTCHA or one-time code appears.

When should I use Browser Control with Omowright?

Browser Control with Omowright fits situations like: filling in a form or clicking through a site you are already signed into; taking screenshots or running web QA on a JavaScript-rendered page; capturing network traffic or a QA trace in a browser the agent owns; handing a login, CAPTCHA or one-time code step to the user.

How do I install Browser Control with Omowright in Claude Code?

Run `npx skills add code-yeongyu/oh-my-openagent --skill browser -a claude-code`. Or copy the skill folder (packages/shared-skills/skills/browser in code-yeongyu/oh-my-openagent) into .claude/skills/browser in your project. Claude Code loads it when a task matches its description.

How do I install Browser Control with Omowright in Codex?

Run `npx skills add code-yeongyu/oh-my-openagent --skill browser -a codex`. Or copy the skill folder (packages/shared-skills/skills/browser in code-yeongyu/oh-my-openagent) into .agents/skills/browser in your project. Codex loads it when a task matches its description.

Can I use Browser Control with Omowright in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add code-yeongyu/oh-my-openagent --skill browser -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/browser, .gemini/skills/browser, .github/skills/browser and .opencode/skills/browser in your project.

What does Browser Control with Omowright need to run?

Going by SKILL.md and its folder, Browser Control with Omowright needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node). Our summary lists: Node.js, to run the bundled `.mjs` setup scripts; A browser connected through BrowserSkill, for the attached engine.

Does Browser Control with Omowright access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Browser Control with Omowright safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Browser Control with Omowright use?

Browser Control with Omowright has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Browser Control with Omowright use?

About 2.2k tokens (SKILL.md is roughly 8.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.2k tokens, read only when the agent opens those files.

What are the alternatives to Browser Control with Omowright?

Skills that share tags, products or a category with Browser Control with Omowright: Dev Browser Automation (MemTensor/MemOS, 12k stars), Core Guide for agent-browser (vercel-labs/agent-browser, 44k stars), Agent Browser (nanocoai/nanoclaw, 31k stars) and Playwright Bowser (disler/bowser, 265 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Browser Control with Omowright?

code-yeongyu (a GitHub user) maintains it in code-yeongyu/oh-my-openagent, which has 69,850 GitHub stars. The repository holds 44 skills in this directory. The repository was last updated on October 7, 2026.

Source: code-yeongyu/oh-my-openagent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.