Vibium is a browser automation tool that lets coding agents navigate web pages, fill forms, click controls, and capture screenshots. It can be used through a command-line skill, an MCP server, or client libraries for JavaScript/TypeScript, Python, and Java. The catalogue add-ons give agents access to Vibium's browser verification workflows.
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 VibiumDev/vibium --skill browsergit clone --depth 1 https://github.com/VibiumDev/vibiumWrote 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/vibiumdev/vibium/browser)<a href="https://agentmods.dev/skills/vibiumdev/vibium/browser"><img src="https://agentmods.dev/badge/skills/vibiumdev/vibium/browser/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/vibiumdev/vibium/browser"><img src="https://agentmods.dev/badge/skills/vibiumdev/vibium/browser.svg" alt="Reviewed on agentmods" width="80" 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.00044 | $0.05165 |
| Opus 5 | $0.00022 | $0.02583 |
| Sonnet 5 | $0.00009 | $0.01033 |
| Haiku 4.5 | $0.00004 | $0.00517 |
Grade A, and why
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 4d 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 — 454 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibium Browser Automation — CLI Reference
The vibium CLI automates Chrome (and Firefox, via --engine firefox) from the command line. The browser auto-launches on first use (daemon mode keeps it running between commands).
Use this skill for browser automation, exploration, debugging, and recording.
Choose explicit CLI commands when you know the steps, or use vibium run
when a model should work out how to accomplish a browser goal.
For an independent acceptance verdict, use the check skill if installed,
or vibium check "<claim>". Run’s completed result and your own browser
observations do not substitute for that invocation.
Core Workflow
For direct browser commands, use this pattern:
- Navigate:
vibium go <url> - Map:
vibium map(get element refs like@e1,@e2) - Interact: Use refs to click, fill, select — e.g.
vibium click @e1 - Re-map: After navigation or DOM changes, get fresh refs with
vibium map
Binary Resolution
Before running any commands, resolve the vibium binary path once:
- Try
vibiumdirectly (works if globally installed vianpm install -g vibium) - Fall back to
./clicker/bin/vibium(dev environment, in project root) - Fall back to
./node_modules/.bin/vibium(local npm install)
Run vibium --help (or the resolved path) to confirm. Use the resolved path for all subsequent commands.
Windows note: Use forward slashes in paths (e.g. ./clicker/bin/vibium.exe) and quote paths containing spaces.
Browser readiness
During initial setup, run vibium ready browser --json with the engine/channel
that the workflow will use. It inspects installed browser and driver files
without launching them or touching existing sessions. Passing confirms the
installation, not browser launch or BiDi connectivity. If installation is missing, use the reported vibium install
command and retry. Direct browser work does not need AI configuration.
Do not rerun readiness before every action when setup is unchanged.
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.
- 4d ago First seen · 454 lines · 44 tokens per session scan A 1e8919fa8313
browser is a skill published in the GitHub repository VibiumDev/vibium (2,933 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 5,165 once invoked, about $0.0002 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-09-08.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
azure-messaging-webpubsub-java
Build real-time web applications with Azure Web PubSub SDK for Java. Use when implementing WebSocket-based messaging, live updates, chat applications, or server-to-client push notifications.
google-safe-browsing
Prevent and fix Google Safe Browsing "Dangerous site" flags. Use when launching a public web app, buying/picking a domain, building a login or signup page, or when any site shows a red "Dangerous site" / "Deceptive site" warning in Chrome, Brave, Safari, Firefox, or Edge. Triggers on "dangerous site", "deceptive…