dev-browser: Instructions file for Codex

AGENTS.md

dev-browser AGENTS.md is an instructions file for Codex, OpenCode from SawyerHood/dev-browser. It costs 209 tokens per session, scanned A, original, MIT.

Repository instructions for dev-browser, a browser-automation tool with a Rust command-line program and a Node.js background service. They specify which tools to use and how to validate changes.

In plain words
What is it for?
Developing the browser daemon and command-line program, running type checks and tests, bundling the daemon, and rebuilding the packaged application.
Why use it?
They prevent incompatible tooling choices and ensure embedded browser code is rebuilt before the Rust program packages it.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is SawyerHood/dev-browser's own configuration. It tells Codex and OpenCode how to work on dev-browser 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 dev-browser configures →

About the project

dev-browser lets coding agents control a Chrome browser with JavaScript while keeping pages and tabs available between calls. Agents use it to navigate websites, inspect accessible page structures, perform actions, and verify results.

SawyerHood/dev-browser · 6,701 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to SawyerHood/dev-browser. 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/SawyerHood/dev-browser/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/SawyerHood/dev-browser

Made for: Codex, OpenCode.

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

README.md
[![agentmods](https://agentmods.dev/badge/instructions/sawyerhood/dev-browser/agents-md/github.svg)](https://agentmods.dev/instructions/sawyerhood/dev-browser/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/sawyerhood/dev-browser/agents-md"><img src="https://agentmods.dev/badge/instructions/sawyerhood/dev-browser/agents-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 dev-browser AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/sawyerhood/dev-browser/agents-md"><img src="https://agentmods.dev/badge/instructions/sawyerhood/dev-browser/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 209 This file is loaded in full into every session.
When invoked 209 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.00209 $0.00209
Opus 5.5 $0.00084 $0.00084
Sonnet 5.5 $0.00042 $0.00042
Haiku 4.5 $0.00021 $0.00021

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

Security

Grade A, and why

dev-browser 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 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.

AGENTS.md · 32 lines

What it actually says

Repository guide

This repository ships dev-browser, a Bun-compiled browser automation CLI and warm daemon built on Puppeteer.

Tooling

  • Use Bun for dependency installation, builds, tests, and TypeScript tooling. Do not use pnpm.
  • The npm package contains a small Node-compatible shim and download scripts; test those under Node as well as Bun.
  • docs/help.md is embedded into the binary and is the source of truth for dev-browser --help.

Validation

Run before finishing runtime changes:

bun install --frozen-lockfile
bun x tsc --noEmit
bun run build
bun run test

For packaging or release changes, also run:

npm pack --dry-run
dist/dev-browser --version
dist/dev-browser --help | head -n 1

Tests that launch Chrome should set DEV_BROWSER_HOME to a temporary directory. Never point tests at a user's real ~/.dev-browser/v1 state.

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 · +3 lines · -38 tokens per session 9deb4c9c6b0d
  2. 1mo ago First seen · 29 lines · 247 tokens per session scan A 87b2b779bf0f

Subscribe to this mod's changes

dev-browser AGENTS.md is an instructions file published in the GitHub repository SawyerHood/dev-browser (6,701 stars, last pushed 8d ago), licensed MIT. It adds 209 tokens to every session, about $0.0008 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-30.

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,786 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,731 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