browser-relay

browser-relay is a skill for Claude Code from reliefeai/browser-relay. It costs 86 tokens per session (3,584 once invoked), scanned A, original, MIT.

A way to control Chrome tabs that are already open and logged in. It works with the user’s existing browser session instead of starting a separate browser.

In plain words
What is it for?
Use it to navigate protected websites, inspect page content, fill forms, click controls, scroll, take screenshots, and run page JavaScript.
Why use it?
It lets an agent work with sites that require existing cookies, single sign-on, extensions, or intranet access. The user can keep using the foreground tab while another tab is controlled.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; mentions Codex.

Part of the browser-relay plugin — 1 skill shipped together

Install

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.

agentmods
npx agentmods add skills/reliefeai/browser-relay/browser-relay
Any agent
npx skills add reliefeai/browser-relay --skill browser-relay
Clone the repo
git clone --depth 1 https://github.com/reliefeai/browser-relay

Made for: Claude Code.

Or install browser-relay, the plugin that ships this one along with the rest of its 1 skill.

Wrote 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.

agentmods badge for browser-relay

README.md
[![agentmods](https://agentmods.dev/badge/skills/reliefeai/browser-relay/browser-relay.svg)](https://agentmods.dev/skills/reliefeai/browser-relay/browser-relay)
Your own site
<a href="https://agentmods.dev/skills/reliefeai/browser-relay/browser-relay"><img src="https://agentmods.dev/badge/skills/reliefeai/browser-relay/browser-relay.svg" alt="Measured on agentmods" height="20"></a>
Per session 86 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,584 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00086 $0.03584
Opus 5 $0.00043 $0.01792
Sonnet 5 $0.00017 $0.00717
Haiku 4.5 $0.00009 $0.00358

Measured 6d ago against content hash 5e2b8ac45251, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

browser-relay scanned grade A with 1 finding 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 6d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

interaction. Do not hand-write `curl` for normal agent browsing tasks. The CLI
skills/browser-relay/SKILL.md · 361 lines

How it starts

The opening of the file, as written. The whole thing — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Browser Relay Skill

Work alongside the user in the Chrome they already use. Browser Relay lets the agent operate existing tabs through a Skill + CLI, including background tabs, without launching a blank browser profile or repeatedly pulling Chrome to the foreground. Remote Relay can reach the user's explicitly enabled browser on another machine.

Use Browser Relay For

Use Browser Relay when you need to:

  • Share the user's current Chrome — keep their existing tabs, cookies, extensions, and login state
  • Interact with login-protected sites — including SSO, intranet pages, dashboards, Gmail, Notion, and similar apps
  • Work without interrupting the foreground tab — select a specific background tab and keep the user's current tab in place
  • Reach another machine — use Remote Relay only after the user explicitly enables it on that browser
  • Handle dynamic pages — JavaScript-rendered content and SPAs
  • Perform actions — click buttons, fill forms, scroll, take screenshots
  • Get structured page text — annotated DOM snapshot with [link], [button], [input] markers
  • Evaluate arbitrary JavaScript in the page context

When NOT to use:

  • Simple static pages without login — use WebFetch or Jina Reader (faster, cheaper)
  • Pure API calls — use the site's REST API directly

Prerequisites

Check setup before the first browser action:

browser-relay doctor

If browser-relay is not installed, tell the user to install the open-source CLI, then rerun the check:

npm install -g @linsoai/browser-relay
browser-relay path

The user must load the directory printed by browser-relay path from chrome://extensions and explicitly enable the extension. Do not install it, enable Remote Relay, or invent a Remote Device ID without the user. A ready setup has the relay server running, the extension connected, and at least one regular Chrome tab attached.

Connection Info

Relay URL:  http://127.0.0.1:18795
WebSocket:  ws://127.0.0.1:18795/extension

Read the full file on GitHub · 361 lines

Changes

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.

  1. 6d ago First seen · 361 lines · 86 tokens per session scan A 5e2b8ac45251

Subscribe to this mod's changes

browser-relay is a skill published in the GitHub repository reliefeai/browser-relay (125 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 3,584 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

webclaw3

浏览器自动化 / 网页数据采集 / 爬虫抓取——用你自己的 Chrome 和已登录状态干活,不用重新登录、不用交账号密码、不怕反爬。所有需要操作浏览器的活都走这个 skill。 场景一(日常上网干活):搜东西、看网页、查数据、抓列表、导表格、下载内容,或者在网站里动手操作——点按钮、填表单、发内容、和商家聊天;包括必须登录才能看的页面,如小红书、抖音、微博、推特(X)、知乎、B站、公众号、淘宝、拼多多、Shopify 后台等。 场景二(沉淀成 skill):任务跑通了,用户说"帮我提炼""以后每天自动跑",把这次探索固化成可反复运行、零 token 的本地脚本 skill,可配定时任务。 场景三(修复):网站改版导致之前生成的…

fatmind/webclaw3 · 272 tokens

aipex-browser

AI-powered browser automation using the AIPex Chrome Extension via MCP bridge. Use this skill when the agent needs to control a Chrome browser — navigating pages, clicking elements, filling forms, capturing screenshots, managing tabs, or downloading content — by connecting to the AIPex MCP bridge.

AIPexStudio/AIPex · 61 tokens

owb

Open Web Bridge (OWB) — drive the user's own real browser with the owb command. Read pages behind their existing logins, gather and cross-check information, fill forms, walk multi-step flows, debug their site, audit responsive/accessibility behavior, and capture or reverse-engineer network traffic. Use this whenever…

woniu9524/open-web-bridge · 143 tokens

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.

koltyakov/browser-bridge · 49 tokens

website-explorer

Discover website capabilities from user behaviors. Learn APIs and automate workflows.

EndymionLee/PilotBrowseMCP · 17 tokens

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.

DeliciousBuding/codex-browser-bridge · 41 tokens