Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add woniu9524/open-web-bridge --skill owbgit clone --depth 1 https://github.com/woniu9524/open-web-bridgeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/woniu9524/open-web-bridge/owb)<a href="https://agentmods.dev/skills/woniu9524/open-web-bridge/owb"><img src="https://agentmods.dev/badge/skills/woniu9524/open-web-bridge/owb.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00143 | $0.08215 |
| Opus 5 | $0.00072 | $0.04108 |
| Sonnet 5 | $0.00029 | $0.01643 |
| Haiku 4.5 | $0.00014 | $0.00822 |
Grade A, and why
owb scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 581 lines — stays where its author put it; the contents beside it link to each section on GitHub.
owb (Open Web Bridge) — driving the user's real browser
owb, the Open Web Bridge CLI, operates the browser the user is using right
now: their logged-in accounts, their settings, their open tabs. That is why you
can reach content that exists only behind a login, and complete actions that
require an identity.
For the same reason, every step lands on a real person's account and they may be using this browser beside you. Read freely; ask before changing anything; open pages in new tabs so you don't take over what they are looking at.
How to use this document
In a hurry? Read "Before you start" → "The shape of a task" → "The core loop".
This file is the trunk; five reference files live in references/, read on demand:
| File | When to read it |
|---|---|
references/commands.md |
Arguments, defaults, limits and return fields — check before writing a complex call instead of guessing argument names |
references/recipes.md |
Longer recipes for a specific job: extraction, clicking quirks, drag/canvas, downloads, site debugging, responsive audits, logins, flows |
references/debugging.md |
Debugging and reverse-engineering: capture, HAR processing, hooks, breakpoints, script patching, offline signature verification |
references/field-notes.md |
Long-tail oddities seen in the field (the "Reality check" table below is the symptom index — come here once a symptom matches) |
references/relay.md |
The user asks about remote-controlling their browser, or daemon-status reports relay mode |
For anything not documented here: this file cannot cover all 80 commands.
owb help lists all 16 groups, owb help <group> expands one, and
owb call <tool> --args '<json>' calls any underlying tool directly.
Don't guess command names — look them up.
Before you start
owb # self-check
✓ daemon+✓ extension connected→ go✗ extension not connected→ stop and tell the user to click the extension icon in their toolbar and check its status. Hammering the tools will only produceNO_EXTENSIONforever.- Command not found →
npm i -g open-web-bridge, thenowb setup [owb] daemon not running, starting it…on stderr during the first command is not an error — the CLI is starting the daemon. Wait for it to connect; don't report it as a fault.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 581 lines · 143 tokens per session scan A 50df37cc8996
owb is a skill published in the GitHub repository woniu9524/open-web-bridge (115 stars, last pushed 15d ago), licensed MIT. It adds 143 tokens to every session and 8,215 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
chrome-agent
Local browser automation with structured, verified outcomes. Use for web navigation, scraping and extraction, form interaction, screenshots and downloads, network or console checks, responsive testing, or page-scoped device emulation.
scrape-structured-data
Get the repeating records off a web page (product grids, search results, job listings, news feeds, tables) as JSON, without writing CSS selectors and without spending a model call to read the HTML. Works on sites with no API, including ones behind a login or bot protection. Runs locally, one binary, no API key. Use…
codex-control-chrome-mcp
Use Codex Control Chrome MCP to control the user's normal Chrome profile through the Codex Chrome extension. Use when a task needs existing Chrome tabs, cookies, logged-in sessions, installed extensions, CDP commands, page inspection, navigation, screenshots, network/console events, or browser automation from an MCP…
control-chrome-bridge
Drive the user's real Chrome browser — their own profile, tabs, cookies and logged-in sessions — through the chrome-bridge MCP server. Use for tasks that need existing browser state: reading a page behind a login, filling a form on a site the user is signed into, testing a local app in a real browser, or inspecting…
browser-bridge
Token-efficient Chrome tab inspection, interaction, and patching via local bridge extension (CLI: bbx). Reads live DOM, styles, console, network, and storage from a real Chrome tab with lower token cost than screenshots.
codex-browser
Control Chrome via Codex Desktop's browser bridge. 52 MCP tools for tabs, navigation, DOM, input, CDP, network, file upload, dialog handling, and diagnostics.