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 agentmods add instructions/quaylabshq/browserops/agents-mdgit clone --depth 1 https://github.com/quaylabshq/browseropsWhat 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 | $0.04727 | $0.04727 |
| Opus 5 | $0.02364 | $0.02364 |
| Sonnet 5 | $0.00945 | $0.00945 |
| Haiku 4.5 | $0.00473 | $0.00473 |
Grade A, and why
browserops AGENTS.md 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.
How it starts
The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
browserops — agent instructions
Guidance for any MCP-compatible coding agent (Claude Code, Cursor, Zed, Continue, Windsurf, custom SDK agents) working in this repo or consuming the browserops MCP server. Claude Code auto-loads this file via the CLAUDE.md symlink.
Project overview
browserops is an MCP server that drives the user's live Chrome profile. Three components in one pnpm workspace:
MCP client (Claude Code / Cursor / Zed / …)
│ stdio MCP (JSON-RPC)
▼
packages/bridge — Node process: MCP server + WebSocket server + rate limiter + risky-action gate + procedure runtime
│ WebSocket on 127.0.0.1:57321, token-authed
▼
packages/extension — Chrome MV3 extension: background service worker + content scripts + popup + options
│ chrome.tabs / chrome.scripting / chrome.debugger
▼
user's real Chrome tabs (with existing logins intact)
packages/shared holds protocol types, error codes, the tool catalogue, and the procedure schema — consumed by both bridge and extension.
Tool naming. MCP tools use underscore form (browser_navigate, procedures_search) to stay within the MCP-spec ^[a-zA-Z0-9_-]+$ pattern. Procedure names (e.g. tempmail.get_email) are internal identifiers and stay dotted — they're YAML filenames, not MCP tool names.
Wire protocol. The bridge translates each MCP tools/call into a WebSocket {type:"request", id, method, params, timeout_ms} envelope. The extension routes method to a handler registered in packages/extension/src/background/handlers/. Responses go back as {type:"response", id, ok, result|error}.
Procedure runtime. Named, parameterised action graphs stored under ~/browserops/procedures/ as YAML. Five procedures_* tools (search, get, save, delete, execute) manage them. The store ships empty — new procedures are authored on-demand by the browserops-teach skill (autonomous) or by hand.
Where to look
| Want to understand… | File |
|---|---|
| The tool catalogue (names, schemas, descriptions) | packages/shared/src/tools.ts |
| MCP dispatch pipeline (validate → rate-limit → risky-gate → forward) | packages/bridge/src/mcp-server.ts |
| Bridge↔extension WebSocket protocol | packages/shared/src/protocol.ts + packages/bridge/src/ws-server.ts + packages/extension/src/background/ws-client.ts |
| Extension handlers (what actually runs in Chrome) | packages/extension/src/background/handlers/ |
| Procedure YAML schema + search ranker | packages/shared/src/procedures.ts + packages/bridge/src/procedures/ |
| Error codes + WebSocket close codes | packages/shared/src/errors.ts |
| Rate limiter + risky-action gate | packages/bridge/src/rate-limiter.ts + packages/bridge/src/safety.ts |
| browserops-teach skill (autonomous procedure authoring, replaces teach + autoteach) | ~/.claude/skills/browserops-teach/SKILL.md (mirror at skills/browserops-teach.md) |
| User-facing setup (registration for every major MCP client) | README.md |
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.
- 2d ago First seen · 228 lines · 4,727 tokens per session scan A 6faacbd71ab6
browserops AGENTS.md is an instructions file published in the GitHub repository quaylabshq/browserops (5 stars, last pushed 1mo ago), licensed MIT. It adds 4,727 tokens to every session, about $0.0236 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-31.
Other instructions, from other repositories
Browser4 CLAUDE.md
Instructions for platonai/Browser4, covering browser4 — project context for claude, architecture, key dispatch chain (cli → browser), batch commands and e2e test structure.
spring-ai-agentcore AGENTS.md
Instructions for spring-ai-community/spring-ai-agentcore, covering agents.md, project overview, architecture, key components and artifact store classes.
flyto-core CLAUDE.md
Instructions for flytohub/flyto-core, covering claude notes, cross-agent handoff and shared code intelligence.
deckforge AGENTS.md
Instructions for tph-kds/deckforge, covering deckforge agent entry point, code intelligence, read order, default routing and non-negotiable implementation rules.
fast-browser CLAUDE.md
Claude Code instructions for m4ttstack/fast-browser, covering fast browser plugin, where a change belongs, fork branch: use fast-browser-runtime, releasing a new runtime and re-pinning this repo: use the script.
agentoscope AGENTS.md
Instructions for rafaelcg/agentoscope, covering agentoscope — agent instructions, what this is, layout, commands and conventions.