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/sawyerhood/dev-browser/agents-mdgit clone --depth 1 https://github.com/SawyerHood/dev-browserWhat 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.00247 | $0.00247 |
| Opus 5 | $0.00123 | $0.00123 |
| Sonnet 5 | $0.00049 | $0.00049 |
| Haiku 4.5 | $0.00025 | $0.00025 |
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 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.
What it actually says
CLAUDE.md
This repository ships dev-browser: a Rust CLI plus a Node.js daemon for browser automation with a QuickJS sandbox. Use this file as the repo-specific guide when making code changes.
Tooling
- Use Node.js tooling for
daemon/and Cargo forcli/. Do not use Bun. - The daemon package uses
pnpm. - The repo root contains packaging glue (
bin/,scripts/,README.md), but most runtime behavior lives incli/anddaemon/.
Validation
Run these before finishing changes that touch runtime code:
cd daemon && npx tsc --noEmit
cd daemon && pnpm vitest run
cd cli && cargo build
If you change daemon runtime code that is embedded into the Rust binary, rebuild the bundles first:
cd daemon && pnpm bundle
cd daemon && pnpm bundle:sandbox-client
cli/src/daemon.rs embeds daemon/dist/daemon.bundle.mjs and daemon/dist/sandbox-client.js via include_str!, so cargo build only sees the latest daemon changes after those bundles are regenerated.
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 · 29 lines · 247 tokens per session scan A 87b2b779bf0f
dev-browser AGENTS.md is an instructions file published in the GitHub repository SawyerHood/dev-browser (6,585 stars, last pushed 1mo ago), licensed MIT. It adds 247 tokens to every session, about $0.0012 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
playwright CLAUDE.md
Claude Code instructions for microsoft/playwright, covering monorepo packages, browser packages, tooling packages, key directories and build.
playwriter AGENTS.md
Instructions for remorses/playwriter, covering backward compatibility, architecture, development, running mcp locally and running cli locally.
actionbook CLAUDE.md
Instructions for actionbook/actionbook, covering claude.md, project overview, architecture, domain model hierarchy and module structure.
apitap CLAUDE.md
Instructions for n1byn1kt/apitap, covering claude.md, using apitap as an mcp tool, commands, architecture and module map.
poster-maker CLAUDE.md
Instructions for dabodamjan/poster-maker, covering poster maker, project purpose, project structure, commands and key rules.
agent-qa AGENTS.md
AGENTS.md instructions for vostride/agent-qa, covering agent-qa agent instructions, branding, repo map, commands and code style.