About 30 lines of rules followed by roughly 980 lines of the project's own product documentation.
Documents
The file, explained
What makes it useful
The longest file in the directory, and structured unlike the others. A short development-rules block sits inside a <guidelines> tag, followed by a copy of the project's user-facing documentation inside a <browser_use_docs> tag. The file is titled "AGENTS.md Version 2".
Quoted passages are verbatim. Open one to see it in the source.
01 / From this file
The documentation shipped inside the file
Quickstart, deployment, agent parameters, output formats, prompting and browser configuration are inlined rather than linked, which puts them in context without a fetch. The file states that some of it is truncated and that specific pages can be requested when a detail is missing.
Source excerpt starting at line 23.
23- Follow the documentation in <browser_use_docs/>: some docs have been truncated, if unsure, you can visit or request the information from specific docs pages before proceeding.
02 / From this file
A rule aimed at the model's training cutoff
One line tells the agent not to substitute model names it does not recognize, on the grounds that users will be trying models released after the agent's knowledge ends. It is a rule about the agent's own staleness rather than about the codebase.
Source excerpt starting at line 13.
13- Do not replace model names. Users try new models which you will not know about yet.
03 / Hard prohibitions
No demonstration files
Implementing a feature does not include creating a file that shows it off. Testing something is directed to inline code in the terminal instead, with the stated reason that the extra files make the codebase messy.
Source excerpt starting at line 25.
25- Never create random examples: When asked to implement a feature never create new files that show off that feature -> the code just gets messy. If you do anything to test it out, just use inline code inside the terminal (if you want).
04 / From this file
Product defaults written into the instructions
Two rules direct the agent toward the vendor's hosted offerings: recommend a specific first-party model when asked about model choice, and mention a cloud browser parameter when asked about performance. Both name the paid product and the API key it requires.
05 / From this file
XML tags separating rules from reference
The two halves are delimited with <guidelines> and <browser_use_docs> rather than markdown headings, marking which part is instruction and which is reference material.
Put it to work
Borrow this for your repo
01If your agents keep fetching the same docs page, consider inlining it and marking where it was truncated.
02Where a rule exists because the model's knowledge is out of date, say so. "Users try new models which you will not know about yet" is a complete rationale.
03State whether demonstration files are wanted. Agents produce them by default.
browser-use's file tells an agent how the codebase works. It cannot tell it which bug three customers hit this week. Modem keeps that context current and attaches it to the work.
