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/nicobailon/surf-cli/surfnpx skills add nicobailon/surf-cli --skill surfgit clone --depth 1 https://github.com/nicobailon/surf-cliWhat 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.00060 | $0.07990 |
| Opus 5 | $0.00030 | $0.03995 |
| Sonnet 5 | $0.00012 | $0.01598 |
| Haiku 4.5 | $0.00006 | $0.00799 |
Grade A, and why
surf 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 3d 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.
surf network.curl --id "req-123" # Generate curl command How it starts
The opening of the file, as written. The whole thing — 749 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Surf Browser Automation
Control Chrome browser via CLI or Unix socket.
Native Host / Socket Notes
For WSL2 with Windows Chrome, run surf install <extension-id> inside WSL2. Surf detects WSL2 and writes the Windows-side native messaging manifest plus a wrapper that launches the WSL host. Use surf install <extension-id> --target linux only for Linux browsers running inside WSLg.
On macOS, Chrome reads the native messaging manifest at ~/Library/Application Support/Google/Chrome/NativeMessagingHosts/surf.browser.host.json. If native messaging fails, confirm that file exists, its allowed_origins extension ID matches chrome://extensions, then rerun surf install <extension-id>, restart Chrome, reload the extension, and inspect the extension service-worker console.
If a command reports Socket connect failed, run surf doctor first, then check the Attempted socket: line. Default sockets are /tmp/surf.sock on macOS/Linux/WSL2 and //./pipe/surf on Windows. If SURF_SOCKET is set, the browser-launched host and the shell running surf must use the same value.
Remote Surf
Remote clients require a per-client credential; Tailnet reachability alone is not authorization. On the POSIX browser host, authorize the client before installing the listener:
surf remote authorize agent-macbook --output ~/agent-macbook.surf-credential.json
surf install <extension-id> --listen 100.101.102.103:4321
surf remote list
Move the mode-0600 credential to the client through a secure channel. It grants full trusted Surf authority. Use it explicitly or through SURF_REMOTE and SURF_REMOTE_CREDENTIAL:
surf --remote 100.101.102.103:4321 \
--remote-credential ~/.config/surf/agent-macbook.json \
page.read
surf remote revoke agent-macbook # Run on the browser host
Remote paths are client-local by default. local:./file is explicit client-local syntax; only remote:/absolute/path accesses the browser host directly. Remote transfer supports one upload or ChatGPT/Gemini input and one screenshot, network-export, or Gemini image output. Limits are 256 MiB per file, 512 MiB and 32 files per connection, and 256 KiB decoded chunks. record, aistudio.build, smoke screenshot directories, directories, and multi-file inputs are not supported remotely. Successful action screenshots and failure --auto-capture diagnostics are transferred back to client-local paths.
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.
- 3d ago First seen · 749 lines · 60 tokens per session scan A 80c12970893a
surf is a skill published in the GitHub repository nicobailon/surf-cli (606 stars, last pushed 3d ago), licensed MIT. It adds 60 tokens to every session and 7,990 once invoked, about $0.0003 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
devloop
Drive Devloop — browser + dev-server on one correlated timeline (web, plus native iOS/Android Expo apps) — by calling its MCP tools as shell commands via mcporter. Use when Devloop's MCP server isn't wired into this agent directly (e.g. a sandboxed or enterprise setup that blocks MCP) but you can run shell commands.
using-claude-in-chrome
Use before controlling Chrome for anything that needs the user's real login session (a tool behind SSO, a Slack UI action, any cookie-gated page) and whenever another browser tool lands on a login page, returns an empty or anonymous-looking page, or seems to have lost a session that worked a moment ago. Also use when…
site-audit
Use when user asks to audit a website, review all pages, check for broken links, capture full site state, or do a comprehensive product review.
kaboom
Use when user asks to check browser state, debug page errors, inspect network traffic, take screenshots, automate clicks or form fills, run accessibility or security audits, measure performance, generate tests, or record browser sessions. Trigger phrases: "check my browser", "debug this page", "take a screenshot"…
control-chrome-cdp
Start or control one exact existing Chrome profile through the Agent OS Chrome CDP bridge with Codex-compatible browser operations. Use for tasks that depend on logged-in Chrome state, including when no Chrome window is open, background tab control, raw CDP, screenshots, page-exposed media saving, or page File…
codex-control-chrome-mcp
Use Codex Control Chrome MCP to control the user's normal Chrome profile through the Codex Chrome extension. Use when a task needs existing Chrome tabs, cookies, logged-in sessions, installed extensions, CDP commands, page inspection, navigation, screenshots, network/console events, or browser automation from an MCP…