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/browser-use/browser-harness/claude-mdgit clone --depth 1 https://github.com/browser-use/browser-harnessWhat 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.00039 | $0.00039 |
| Opus 5 | $0.00019 | $0.00019 |
| Sonnet 5 | $0.00008 | $0.00008 |
| Haiku 4.5 | $0.00004 | $0.00004 |
Grade A, and why
browser-harness 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 yesterday.
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.
What it actually says
Claude Code instructions
Read and follow AGENTS.md.
For browser work in this checkout, use ./browser-harness so the current
source and its default recorder are active.
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.
- yesterday First seen · 7 lines · 39 tokens per session scan A 32400f5804f6
browser-harness CLAUDE.md is an instructions file published in the GitHub repository browser-use/browser-harness (17,240 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session, 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.
Other instructions, from other repositories
terminal AGENTS.md
Instructions for browser-use/terminal, covering agent notes, rust rewrite verification loop and terminal ui testing standard.
core AGENTS.md
Instructions for TideSurf/core, covering tidesurf agent guide, project, architecture, commands and website design.
open-browser-use AGENTS.md
Instructions for iFurySt/open-browser-use, covering open-browser-use, 每轮开始先读, 代码改完前要读, 按任务需要选读 and 工作规则.
open-browser-use CLAUDE.md
Instructions for iFurySt/open-browser-use, a project described as: 🔮 Platform-neutral Browser Use for AI agents: real Chrome automation with a CLI + SDKs, no lock-in, dead simple.
core CLAUDE.md
Instructions for TideSurf/core, a project described as: Connect Chromium to LLM agents via token-efficient DOM compression. 50-200 tokens per page.
browser-use CLAUDE.md
Instructions for browser-use/browser-use, covering claude.md, high-level architecture, core components, event-driven browser management and cdp integration.