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/saik0s/mcp-browser-use/agents-mdgit clone --depth 1 https://github.com/Saik0s/mcp-browser-useWrote 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.
[](https://agentmods.dev/instructions/saik0s/mcp-browser-use/agents-md)<a href="https://agentmods.dev/instructions/saik0s/mcp-browser-use/agents-md"><img src="https://agentmods.dev/badge/instructions/saik0s/mcp-browser-use/agents-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.01631 | $0.01631 |
| Opus 5 | $0.00816 | $0.00816 |
| Sonnet 5 | $0.00326 | $0.00326 |
| Haiku 4.5 | $0.00163 | $0.00163 |
Grade A, and why
mcp-browser-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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Browser Use Development Guidelines
Audience: LLM-driven engineering agents and human developers
MCP server that wraps browser-use for AI-driven browser automation. HTTP-only transport (stdio deprecated due to timeout issues with long-running browser tasks).
Required Development Workflow
CRITICAL: Always run these commands before committing:
uv sync # Install dependencies
uv run ruff format . # Format code
uv run ruff check . # Lint check
uv run pyright # Type checking
uv run pytest # Run tests
All checks must pass - this is enforced by pre-commit hooks. Alternative: just check
Repository Structure
| Path | Purpose |
|---|---|
src/mcp_server_browser_use/ |
Library source code |
├─ server.py |
FastMCP server + MCP tools |
├─ cli.py |
Typer CLI for daemon management |
├─ config.py |
Pydantic settings |
├─ providers.py |
LLM factory (12 providers) |
├─ observability/ |
Task tracking (SQLite persistence) |
├─ research/ |
Deep research workflow |
└─ skills/ |
Machine-learned browser skills |
tests/ |
Pytest test suite |
docs/ |
Design documents |
examples/ |
Example usage |
Core MCP Tools
| Tool | Purpose | Duration |
|---|---|---|
run_browser_agent |
Execute browser automation | 60-120s |
run_deep_research |
Multi-search research | 2-5 min |
skill_list/get/delete |
Skill management | <1s |
health_check |
Server status | <1s |
task_list/get/cancel |
Task management | <1s |
Writing Code
Style Guidelines
- Python 3.11+ with full type annotations
- Line length: 150 characters
- Use async/await for I/O operations
- Follow existing patterns - check similar code first
- Prioritize clarity over cleverness
Code Standards
- Type hints required for all functions
- Docstrings for public APIs
- No
anytypes - use specific types - Async testing with anyio/pytest-asyncio
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.
- 5d ago First seen · 233 lines · 1,631 tokens per session scan A e4d385f220c8
mcp-browser-use AGENTS.md is an instructions file published in the GitHub repository Saik0s/mcp-browser-use (958 stars, last pushed 6mo ago), licensed MIT. It adds 1,631 tokens to every session, about $0.0082 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.