vibesurfer

An agent-controlled headless browser: a real web browser used without a visible window. It can keep browser sessions, pages, authentication state, and an audit record of operations.

In plain words
What is it for?
Use it to open websites, navigate pages, interact with controls, inspect page structure, maintain logged-in sessions, and automate browser-based tasks.
Why use it?
It lets coding agents work with websites while preserving state between actions and recording what happened, which helps with repeatable browser automation.

Skill for Claude CodeCodex

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 skills/frane/vibesurfer/vs-cli
Any agent
npx skills add frane/vibesurfer --skill vs-cli
Clone the repo
git clone --depth 1 https://github.com/frane/vibesurfer

Made for: Claude Code, Codex.

Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,220 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
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.00081 $0.05220
Opus 5 $0.00041 $0.02610
Sonnet 5 $0.00016 $0.01044
Haiku 4.5 $0.00008 $0.00522

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

Security

Grade A, and why

vibesurfer 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.

- One-shot HTTP fetches with no DOM (use `curl`).
Origin

Copies of this mod

1 near-identical copy found in the catalogue:

crates/vs-cli/SKILL.md · 196 lines

How it starts

The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.

vibesurfer (binary: vs)

vs is a stateless CLI that talks to a daemon (vs serve, auto-spawned on first call) over a Unix socket. Not installed? npx vibesurfer <args> runs the same binary (downloaded and cached on first use); vs skill install wires it into every detected agent. The daemon owns one long-lived browser engine on the OS main thread and a SQLite store at ~/.vibesurfer/state.db. Every primitive writes one audit row before returning — there's no opt-out, no untracked operation.

Short forms are the default in agent contexts

Every primitive has a short alias. Long forms exist for human-readable documentation; agent invocations should use the shorter form to save tokens. vs o https://... is the canonical shape for vs open https://..., not the other way around. The 19-primitive tables below lead with the short form and show the long form in parens; both work identically.

Frequent flags also have short forms: -S (--session), -j (--json), -F (--full), -s (--since), -n (--limit), -P (--page). The --token flag stays verbose because it's never typed by hand — you paste it from the previous read.

Use this tool when

  • You need to drive a real browser to read or interact with a web app (login, scrape behind auth, click through SPA state).
  • You need stable refs across snapshots so you can plan a multi-step interaction without scraping coordinates.
  • You want persistent auth (cookies + storage) that survives across sessions, encrypted at rest.
  • You want every action audited automatically — for replay, debugging, or compliance.

Don't use this tool for

  • One-shot HTTP fetches with no DOM (use curl).
  • Anything where you'd be parsing the rendered HTML by string matching — vs_view already gives you a typed accessibility tree with stable refs.
  • Headless screenshots of fixed URLs with no interaction (overkill — though you can; see vs capture).

The 25 primitives

Wire form is vs_<name> (over the socket); CLI subcommand is <name> with hyphens. Each call returns a state envelope (@<token> success, ! CODE error, ? warning lines before the envelope).

Read the full file on GitHub · 196 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. 3d ago First seen · 196 lines · 81 tokens per session scan A ba363196d9c5

Subscribe to this mod's changes

vibesurfer is a skill published in the GitHub repository frane/vibesurfer (15 stars, last pushed 6d ago), licensed Apache-2.0. It adds 81 tokens to every session and 5,220 once invoked, about $0.0004 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.