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 skills/buildoak/fieldwork-skills/browser-opsnpx skills add buildoak/fieldwork-skills --skill browser-opsgit clone --depth 1 https://github.com/buildoak/fieldwork-skillsWrote 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/skills/buildoak/fieldwork-skills/browser-ops)<a href="https://agentmods.dev/skills/buildoak/fieldwork-skills/browser-ops"><img src="https://agentmods.dev/badge/skills/buildoak/fieldwork-skills/browser-ops.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.1 | $0.00029 | $0.05125 |
| Opus 5 | $0.00015 | $0.02563 |
| Sonnet 5 | $0.00006 | $0.01025 |
| Haiku 4.5 | $0.00003 | $0.00513 |
Grade A, and why
browser-ops scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Rule of thumb:** If you can get the data with `curl`, you don't need a browser. How it starts
The opening of the file, as written. The whole thing — 431 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser Ops
Browser automation via agent-browser. 25 tools wrapping Playwright for navigation, interaction, observation, and session management. Validated on two benchmark suites: 12/15 pass on a 15-task suite (100% excluding external blockers), 9/10 on a 10-task progressive suite. Standout: Notion end-to-end signup with AgentMail OTP verification.
Terminology used in this file:
- Playwright: A browser automation framework that lets tools control Chromium/Chrome.
- a11y tree: The accessibility tree (screen-reader-friendly page structure) used by
browser_snapshot. - DOM: Document Object Model, the browser's structured representation of page elements.
- CSS selector: A rule for targeting specific DOM elements (for example
.priceor#submit). - OAuth: A standard login/authorization flow that redirects through an identity provider (for example, "Sign in with GitHub").
Setup
npm install -g @anthropic-ai/agent-browser
agent-browser start
- Claude Code: copy this skill folder into
.claude/skills/browser-ops/ - Codex CLI: append this SKILL.md content to your project's root
AGENTS.md
For the full installation walkthrough (prerequisites, verification, troubleshooting), see references/installation-guide.md.
Staying Updated
This skill ships with an UPDATES.md changelog and UPDATE-GUIDE.md for your AI agent.
After installing, tell your agent: "Check UPDATES.md in the browser-ops skill for any new features or changes."
When updating, tell your agent: "Read UPDATE-GUIDE.md and apply the latest changes from UPDATES.md."
Follow UPDATE-GUIDE.md so customized local files are diffed before any overwrite.
Quick Start
The simplest possible browser flow: navigate, inspect, capture.
browser_navigate(url="https://example.com")
browser_snapshot(mode="interactive")
browser_screenshot(path="/tmp/example.png")
browser_close()
What ships with it
22 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/anti-detection-guide.md 13 KB
- references/battle-tested-patterns.md 17 KB
- references/failure-log.md 12 KB
- references/installation-guide.md 3.6 KB
- references/playbooks/booking-com.md 6.2 KB
- references/playbooks/cloudflare-sites.md 7.3 KB
- references/playbooks/google-flights.md 5.3 KB
- references/playbooks/headed-browser-setup.md 12 KB
- references/playbooks/linear-signup.md 5.3 KB
- references/playbooks/notion-signup.md 5.4 KB
- references/playbooks/reddit-scraping.md 4.7 KB
- references/playbooks/stripe-iframe.md 5.3 KB
- references/playbooks/wikipedia-extraction.md 6.5 KB
- references/stealth-config.md 6.7 KB
- references/test-results.md 15 KB
- references/tool-inventory.md 12 KB
- scripts/agentmail.sh 3.8 KB runs code
- scripts/browser-check.sh 4.8 KB runs code
- scripts/mailbox.py 7.9 KB runs code
- scripts/requirements.txt 18 B
- UPDATE-GUIDE.md 2.5 KB
- UPDATES.md 3.7 KB
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 · 431 lines · 29 tokens per session scan A 65d0fd565323
browser-ops is a skill published in the GitHub repository buildoak/fieldwork-skills (15 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 5,125 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
x402
Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — "just use it" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing…
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.
remote-browser
Controls an isolated Browser Use Cloud browser from a sandboxed machine with the current Browser Use CLI.
cloud
Documentation reference for using Browser Use Cloud — the hosted API and SDK for browser automation. Use this skill whenever the user needs help with the Cloud REST API (v2, v3, or v4), browser-use-sdk (Python or TypeScript), X-Browser-Use-API-Key authentication, cloud sessions, browser profiles, profile sync, CDP…
opencli-browser
Use when an agent needs to drive a real Chrome window via opencli — inspect a page, fill forms, click through logged-in flows, or extract data ad-hoc. Covers the selector-first target contract, compound form fields, stale-ref handling, network capture, and the agent-native envelopes the CLI returns. Not for writing…
opencli-adapter-author
Use when writing an OpenCLI adapter for a new site or adding a new command to an existing site. Guides end-to-end from first recon through field decoding, adapter coding, and verify. Replaces opencli-oneshot / opencli-explorer. For ad-hoc browser driving (no adapter), see opencli-browser instead; for a top-level…