chrome-use AGENTS.md

A set of instructions for coding agents working on the chrome-use project. It covers the package manager, code style, command-line flags, documentation, and dashboard work.

In plain words
What is it for?
Use it when modifying the chrome-use codebase, especially when installing dependencies, changing CLI behavior, or updating user-facing features.
Why use it?
It prevents agent changes from conflicting with the project’s required tools, naming rules, and documentation process.

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

Made for: Codex, OpenCode.

Per session 2,202 This file is loaded in full into every session.
When invoked 2,202 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin fork From a forked repository.
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.02202 $0.02202
Opus 5 $0.01101 $0.01101
Sonnet 5 $0.00440 $0.00440
Haiku 4.5 $0.00220 $0.00220

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

Security

Grade A, and why

chrome-use 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.

AGENTS.md · 211 lines

How it starts

The opening of the file, as written. The whole thing — 211 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 the NO_COLOR environment 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., --autoConnect is wrong).

Documentation

When adding or changing user-facing features (new flags, commands, behaviors, environment variables, etc.), update all of the following:

  1. cli/src/output.rs--help output (flags list, examples, environment variables)
  2. README.md — Options table, relevant feature sections, examples
  3. skill-data/core/SKILL.md (and its references/) — so AI agents know about the feature when they load the core skill. Edit skill-data/core/SKILL.md for overview/workflow changes; edit skill-data/core/references/*.md for detailed reference content. Do not put feature content in skills/chrome-use/SKILL.md — that file is an intentionally thin discovery stub for npx skills add and exists only to redirect agents to chrome-use skills get core.
  4. docs/src/app/ — the Next.js docs site (MDX pages)
  5. 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.

In the docs/src/app/ MDX files, always use HTML <table> syntax for tables (not markdown pipe tables). This matches the existing convention across the docs site.

Read the full file on GitHub · 211 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 · 211 lines · 2,202 tokens per session scan A 7f6c1a1d355a

Subscribe to this mod's changes

chrome-use AGENTS.md is an instructions file published in the GitHub repository leeguooooo/chrome-use (156 stars, last pushed 3d ago), licensed Apache-2.0. It adds 2,202 tokens to every session, about $0.0110 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.