BrowserMesh: Instructions file for Claude Code

CLAUDE.md

BrowserMesh CLAUDE.md is an instructions file for Claude Code from scrollDynasty/BrowserMesh. It costs 1,792 tokens per session, scanned A, original, Apache-2.0.

Project instructions for BrowserMesh, a local runtime that manages separate browser sessions for external MCP clients such as Claude Code or Codex.

In plain words
What is it for?
Developing or operating BrowserMesh while preserving explicit session and page addressing, separated browser-engine adapters, and the project’s architectural boundaries.
Why use it?
They clarify which component is responsible for reasoning and orchestration, and which component only performs browser work.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions subagents; mentions Claude Code; mentions AGENTS.md.

This is scrollDynasty/BrowserMesh's own configuration. It tells Claude Code how to work on BrowserMesh itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything BrowserMesh configures →

Reuse

Borrowing it

Nothing to install: this file belongs to scrollDynasty/BrowserMesh. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/scrollDynasty/BrowserMesh/master/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/scrollDynasty/BrowserMesh

Made for: Claude Code.

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 BrowserMesh CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/scrolldynasty/browsermesh/claude-md/github.svg)](https://agentmods.dev/instructions/scrolldynasty/browsermesh/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/scrolldynasty/browsermesh/claude-md"><img src="https://agentmods.dev/badge/instructions/scrolldynasty/browsermesh/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for BrowserMesh CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/scrolldynasty/browsermesh/claude-md"><img src="https://agentmods.dev/badge/instructions/scrolldynasty/browsermesh/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,792 This file is loaded in full into every session.
When invoked 1,792 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.01792 $0.01792
Opus 5.5 $0.00717 $0.00717
Sonnet 5.5 $0.00358 $0.00358
Haiku 4.5 $0.00179 $0.00179

Measured 1mo ago against content hash 45227c2ee118, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

BrowserMesh CLAUDE.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 1mo 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.

CLAUDE.md · 143 lines

How it starts

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

BrowserMesh

Local isolated multi-session browser runtime, driven by external MCP clients.

AGENTS.md is the full charter. This file is the working subset; when the two disagree, AGENTS.md wins.

Responsibility boundary

User → external AI client → MCP → BrowserMesh → isolated browser sessions

The external client (Claude Code, Codex, Cursor, Qwen, …) does the reasoning, planning, and orchestration. BrowserMesh only executes browser work.

Never add internal Agent entities or registries, browser_agent_* / browser_message_* tools, agent mailboxes or messaging, LLM-owned session principals, internal LLM calls, or reasoning loops inside BrowserMesh. Session name and metadata are neutral workflow labels — not principals, permissions, identities, or leases.

Architecture invariants

BrowserMesh is an independent runtime, not a wrapper around Playwright MCP. MCP is a transport adapter; Playwright is a browser-engine adapter. Domain, application, and runtime code import neither.

  • Explicit addressing. Every browser operation targets an explicit sessionId; every page-specific operation an explicit pageId. There is never a global currentSession, activeSession, currentPage, activePage, or currentTab.
  • Context isolation. Each ready session owns its own non-persistent Chromium BrowserContext.
  • Page isolation. A pageId from another session is rejected.
  • Per-session serialization. Everything touching one session's live browser state goes through that session's serial queue — including read-style operations (snapshot, URL, title, visible text). They must not bypass an in-progress operation.
  • Cross-session parallelism. Different sessions run concurrently. Never introduce one global browser-operation mutex.
  • Queue recovery. A rejected, failed, or timed-out operation must not poison a session queue; subsequent accepted operations still execute.
  • Lifecycle safety. Close and shutdown must not race initialization into leaked contexts or pages. An unexpected Chromium disconnect must not silently rebuild live sessions.

Read the full file on GitHub · 143 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. 1mo ago Changed 45227c2ee118
  2. 1mo ago Changed · +7 lines · +79 tokens per session 81a8201d6530
  3. 2mo ago First seen · 136 lines · 1,713 tokens per session scan A 4618de87907e

Subscribe to this mod's changes

BrowserMesh CLAUDE.md is an instructions file published in the GitHub repository scrollDynasty/BrowserMesh (3 stars, last pushed 2d ago), licensed Apache-2.0. It adds 1,792 tokens to every session, about $0.0072 per session on Opus 5.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.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens