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 skills add VibeTechnologies/vibe-mcp --skill setupgit clone --depth 1 https://github.com/VibeTechnologies/vibe-mcpWrote 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/vibetechnologies/vibe-mcp/setup)<a href="https://agentmods.dev/skills/vibetechnologies/vibe-mcp/setup"><img src="https://agentmods.dev/badge/skills/vibetechnologies/vibe-mcp/setup.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.00063 | $0.01014 |
| Opus 5 | $0.00032 | $0.00507 |
| Sonnet 5 | $0.00013 | $0.00203 |
| Haiku 4.5 | $0.00006 | $0.00101 |
Grade A, and why
setup 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 7d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up Vibe Browser
The vibe MCP server is only a relay. It has no browser of its own: it forwards
tool calls to the Vibe Chrome extension running in the user's real Chrome. Until
that extension is installed and connected, every browser tool will fail.
Work through the steps below in order. Stop as soon as Step 4 verifies.
Step 1 — Install the Vibe extension
Ask the user to install the extension in Chrome, Brave, or any Chromium browser:
Chrome Web Store (recommended) https://chromewebstore.google.com/detail/vibe-ai-browser-co-pilot/djodpgokbmobeclicaicnnidccoinado
Click Add to Chrome. The Vibe icon appears in the toolbar.
Developer version (if the store is blocked)
- Download https://github.com/VibeTechnologies/VibeWebAgent/releases/latest/download/vibe-ai-copilot-latest.zip
- Extract it to a permanent folder (deleting it later uninstalls the extension).
- Open
chrome://extensions, turn on Developer mode. - Click Load unpacked and select the extracted folder.
Step 2 — Turn on external control
The extension refuses external control until the user opts in:
- Click the Vibe icon in the Chrome toolbar.
- Open Settings.
- Enable MCP External Control.
- The status indicator should read Connected.
Chrome must stay open. Closing the browser drops the connection.
Step 3 — Choose local or remote
Local (default). Claude Code and Chrome are on the same machine. Nothing more to configure — the server auto-spawns a localhost relay daemon and the extension finds it.
Remote. Chrome runs on a different machine from Claude Code (for example Claude Code on a dev box, Chrome on the user's laptop). This needs no inbound port:
- In the extension Settings, switch to Remote mode.
- Copy the remote UUID it shows.
- Pass it to the server, either as an argument (
--remote <uuid>) or via theVIBE_REMOTE_URLenvironment variable.
The remote UUID is the only bearer credential for that browser. Treat it like a password. Never paste it into a file the user tracks in git, and never print it back in full. If it leaks, regenerate it in extension Settings.
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.
- 7d ago First seen · 94 lines · 63 tokens per session scan A f065c8357518
setup is a skill published in the GitHub repository VibeTechnologies/vibe-mcp (3 stars, last pushed 15d ago), licensed Apache-2.0. It adds 63 tokens to every session and 1,014 once invoked, about $0.0003 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-31.
Other skills, from other repositories
Agent Browser Automation
Fast Rust-based headless browser automation CLI with Node.js fallback for AI agents, featuring navigation, clicking, typing, snapshots, and structured commands optimized for agent workflows.
Browser-Use Automation
CLI tool for persistent browser automation with multi-session support, featuring Chromium/Real/Remote browser modes, cookie management, JavaScript execution, and long-running automation workflows.
aginxbrowser
Browser engine for AI agents: fetch JS-rendered and Cloudflare-protected pages as clean markdown, run 5-engine aggregated web search (Baidu, Bing, Sogou, WeChat, Google), take screenshots as visual input, extract structured data from SPAs, and drive multi-step interactions (click, type, fill forms, login, paginate)…
real-browser-control
Connect an AI coding agent to the user's REAL Chrome via Real Browser MCP (local MCP server + Chrome extension over localhost WebSocket). Use for live UI verification, already-open tabs, existing cookies/SSO/2FA, staging admin panels, and any task where headless Playwright or a cloud agentic browser would miss the…
browser-automation
Control the user's real logged-in Chrome via Real Browser MCP (extension + local MCP). Use for live UI checks, existing SSO/cookies, and tabs already open. Triggers: real browser, my Chrome, not headless, verify in browser. Prefer over Playwright when session state matters. Prefer Playwright for CI.
Agent Browser Operator
Interactive browser skill for logged-in flows, dynamic pages, and session-aware site operations.