sendblue-browser-use AGENTS.md

Project instructions for sendblue-browser-use, a Bun and Hono service that controls a Chromium browser through an HTTP API and optional CDP connections.

In plain words
What is it for?
Setting up the browser daemon, installing Chromium, configuring its API key, and using Playwright, Puppeteer, or other CDP clients.
Why use it?
They explain what the repository contains, how to install and start it, and how other browser-automation clients can connect.

Instructions file for CodexOpenCode

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 instructions/sendblue-api/sendblue-browser-use/agents-md
Clone the repo
git clone --depth 1 https://github.com/sendblue-api/sendblue-browser-use

Made for: Codex, OpenCode.

Per session 1,064 This file is loaded in full into every session.
When invoked 1,064 The same file — it is already loaded in full.
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 $0.01064 $0.01064
Opus 5 $0.00532 $0.00532
Sonnet 5 $0.00213 $0.00213
Haiku 4.5 $0.00106 $0.00106

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

Security

Grade A, and why

sendblue-browser-use AGENTS.md 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 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.

Makes network callslowCapability

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

curl -s http://127.0.0.1:8787/health
AGENTS.md · 91 lines

How it starts

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

AGENTS.md — sendblue-browser-use

Spec: https://agents.md. This file is read by Codex, Cursor, Antigravity, Windsurf, Aider, Cline, Jules, Zed, and most other agents that follow the convention.

What this repo is

A standalone HTTP daemon that runs a stealth-patched Chromium (patchright) for browser automation. Long-lived process, bearer-token-gated REST API, optional CDP attach for any client (Playwright, Puppeteer, custom scripts). Passes typical Cloudflare Turnstile and similar low-friction checks; not for hostile scraping at scale.

Source layout:

  • src/ — Bun + Hono HTTP server
  • mcp/ — MCP server wrapper (npm-publishable as sendblue-browser-mcp)
  • skills/sendblue-browser/SKILL.md — cross-agent skill (Claude / Codex / Antigravity / Cline)
  • .claude-plugin/plugin.json — Claude Code plugin manifest
  • examples/ — Playwright / Puppeteer / multi-agent CDP attach snippets
  • Dockerfile + docker-compose.yml — self-contained deploy

Setup

bun install
bun --bun x patchright install chromium
cp .env.example .env
# Set BROWSER_USE_API_KEY (any string ≥ 8 chars; generator: openssl rand -hex 32)
bun run dev          # starts daemon on http://127.0.0.1:8787

Or Docker: docker compose up -d.

Common commands

# Health (no auth)
curl -s http://127.0.0.1:8787/health

# Create a session
curl -s -X POST http://127.0.0.1:8787/sessions \
  -H "Authorization: Bearer $BROWSER_USE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"qa","persistent":false}'

# Navigate (http/https only)
curl -s -X POST http://127.0.0.1:8787/sessions/qa/navigate \
  -H "Authorization: Bearer $BROWSER_USE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com/","waitUntil":"networkidle","timeoutMs":15000}'

# Screenshot
curl -s "http://127.0.0.1:8787/sessions/qa/screenshot?fullPage=true" \
  -H "Authorization: Bearer $BROWSER_USE_API_KEY" -o /tmp/shot.png

# Eval JS — expression form (wrap statements in IIFE)
curl -s -X POST http://127.0.0.1:8787/sessions/qa/script \
  -H "Authorization: Bearer $BROWSER_USE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"code":"(() => document.title)()"}'

Read the full file on GitHub · 91 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. 2d ago First seen · 91 lines · 1,064 tokens per session scan A 84733567f004

Subscribe to this mod's changes

sendblue-browser-use AGENTS.md is an instructions file published in the GitHub repository sendblue-api/sendblue-browser-use (3 stars, last pushed 2mo ago), licensed MIT. It adds 1,064 tokens to every session, about $0.0053 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-31.