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/tidesurf/core/tidesurf-browsernpx skills add TideSurf/core --skill tidesurf-browsergit clone --depth 1 https://github.com/TideSurf/coreWrote 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/tidesurf/core/tidesurf-browser)<a href="https://agentmods.dev/skills/tidesurf/core/tidesurf-browser"><img src="https://agentmods.dev/badge/skills/tidesurf/core/tidesurf-browser.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.00097 | $0.01235 |
| Opus 5 | $0.00048 | $0.00617 |
| Sonnet 5 | $0.00019 | $0.00247 |
| Haiku 4.5 | $0.00010 | $0.00123 |
Grade A, and why
tidesurf-browser 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TideSurf Browser
TideSurf gives you a real Chromium browser. It launches a browser or attaches to a running one over CDP, then compresses the live DOM into token-efficient text annotated with action IDs. You read the page as text, act on elements by ID, and re-read to see the result.
The full input table for every tool is in references/tool-reference.md.
The core loop
Every browser task follows the same loop:
get_stateto read the current page as compact text. Interactive elements are tagged with IDs likeL1(link),B2(button),I3(input).- Pick the element ID that matches your intent.
- Act on it:
click,type,select, orscroll. - Re-read with
get_stateto observe the result.
Element IDs are snapshot-scoped. An ID is valid only for the snapshot that produced it. Navigation, DOM mutations, and most actions invalidate prior IDs. Never reuse an ID from an earlier snapshot; call get_state again and use the fresh IDs. This applies even when the page "looks the same" — re-rendered nodes get new IDs.
Token discipline
Page state is the main context cost. Control it:
- Pass
maxTokenstoget_stateto cap the snapshot size. Start small and raise it only if the element you need is missing. - Pass
viewport: trueto restrict the snapshot to what is on screen. - Use
modeto shape the output:fullfor the complete annotated DOM,minimalfor structure only,interactivefor actionable elements only. Preferinteractivewhen you only need to act. - On huge pages, run
searchwith a query first to locate the relevant region instead of dumping full state. - Use
includeHiddenonly when the element you need is not visible (e.g. collapsed menus).
Forms
typeenters text into an input by ID. Passclear: trueto replace existing content instead of appending.selectsets a<select>element by ID to a given optionvalue.uploadattaches a local file to a file input by ID.filePathmust be a path on the local filesystem.- After submitting a form, treat the page as changed: re-read state before doing anything else.
What ships with it
1 file 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.
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 · 86 lines · 97 tokens per session scan A 1c51a070d5b4
tidesurf-browser is a skill published in the GitHub repository TideSurf/core (21 stars, last pushed 19d ago), licensed Apache-2.0. It adds 97 tokens to every session and 1,235 once invoked, about $0.0005 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 skills, from other repositories
Chrome
Browser automation for the user's Chrome browser. Use for browser tasks that require the user's cookies, logged-in sessions, existing tabs, extensions, or remote authenticated sites.
open-browser-use
Platform-neutral guidance for using Open Browser Use, the open-source Chrome automation stack for AI agents. Use when an agent needs to install, verify, troubleshoot, or operate Open Browser Use through its browser extension, native CLI, JavaScript SDK, Python SDK, Go SDK, or Browser Use style JSON-RPC methods; use…
browser_harness
../../SKILL.md.
browser-use-terminal
Direct browser control via the Browser Use Terminal CLI. Use when the user wants to automate, scrape, test, or interact with web pages — you drive the browser yourself with Python helpers.
browser-harness
Control a real browser via CDP: clicking, typing, navigation, logged-in sessions, JS-rendered or bot-protected pages. Not for plain HTTP fetches of public content - use curl for those.
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…