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/vercel-labs/agent-browser/agents-mdgit clone --depth 1 https://github.com/vercel-labs/agent-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.02259 | $0.02259 |
| Opus 5 | $0.01130 | $0.01130 |
| Sonnet 5 | $0.00452 | $0.00452 |
| Haiku 4.5 | $0.00226 | $0.00226 |
Grade A, and why
agent-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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- antigravity-browser-bridge AGENTS.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Instructions for AI coding agents working with this codebase.
Package Manager
This project uses pnpm. Always use pnpm instead of npm or yarn for installing dependencies, running scripts, etc. (e.g., pnpm install, pnpm run build).
Code Style
- Do not use emojis in code, output, or documentation. Unicode symbols (✓, ✗, →, ⚠) are acceptable.
- In documentation and markdown, never use double hyphens (
--) as a dash. Use an emdash (—) sparingly when needed. Prefer rewriting the sentence to avoid dashes entirely. - CLI colored output uses
cli/src/color.rs. This module respects theNO_COLORenvironment variable. Never use hardcoded ANSI color codes. - CLI flags must always use kebab-case (e.g.,
--auto-connect,--allow-file-access). Never use camelCase for flags (e.g.,--autoConnectis wrong).
Documentation
Do not hard-wrap prose in documentation files such as Markdown, MDX, and READMEs; let the editor or renderer wrap text naturally.
When adding or changing user-facing features (new flags, commands, behaviors, environment variables, etc.), update all of the following:
cli/src/output.rs—--helpoutput (flags list, examples, environment variables)README.md— Options table, relevant feature sections, examplesskill-data/core/SKILL.md(and itsreferences/) — so AI agents know about the feature when they load the core skill. Editskill-data/core/SKILL.mdfor overview/workflow changes; editskill-data/core/references/*.mdfor detailed reference content. Do not put feature content inskills/agent-browser/SKILL.md— that file is an intentionally thin discovery stub fornpx skills addand exists only to redirect agents toagent-browser skills get core.docs/src/app/— the Next.js docs site (MDX pages)- Inline doc comments in the relevant source files
This applies to changes that either human users or AI agents would need to know about. Do not skip any of these locations.
CLI/MCP Parity
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.
- 3d ago First seen · 215 lines · 2,259 tokens per session scan A ddc141989d48
agent-browser AGENTS.md is an instructions file published in the GitHub repository vercel-labs/agent-browser (41,715 stars, last pushed today), licensed Apache-2.0. It adds 2,259 tokens to every session, about $0.0113 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
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.