connect

A command that checks whether OpenChrome can reach a running Chrome browser through the Chrome DevTools Protocol, a browser control interface.

In plain words
What is it for?
Use it to verify the OpenChrome setup, check Chrome's connection status, and see which browser tools are available.
Why use it?
It quickly shows whether the browser connection and server are available before you try browser automation.

Command

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 commands/shaun0927/openchrome/connect
Clone the repo
git clone --depth 1 https://github.com/shaun0927/openchrome
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 239 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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 $0.00032 $0.00239
Opus 5 $0.00016 $0.00120
Sonnet 5 $0.00006 $0.00048
Haiku 4.5 $0.00003 $0.00024

Measured 2d ago against content hash be42b73d8a46, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

connect 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 2d 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.

commands/connect.md · 30 lines

What it actually says

/openchrome:connect

Check that OpenChrome is installed, the MCP server is running, and Chrome is reachable. Then print a one-line summary of the available tool surface.

Steps

  1. Call oc_connection_health to verify the CDP connection and server version.
  2. If status is "ok", respond: "OpenChrome is connected — Chrome is live on <cdp_url>. Server v<version> · <tool_count> tools available."
  3. If status is not "ok", report the error message verbatim and suggest running openchrome doctor in a terminal to diagnose.

Example output

OpenChrome is connected — Chrome is live on ws://127.0.0.1:9222.
Server v1.12.5 · 110 tools available.

Arguments

$ARGUMENTS — ignored; this command takes no arguments.

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. 2d ago First seen · 30 lines · 32 tokens per session scan A be42b73d8a46

Subscribe to this mod's changes

connect is a command published in the GitHub repository shaun0927/openchrome (235 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 239 once invoked, about $0.0002 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.