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 agentmods add skills/vibiumdev/vibium/vibe-checknpx skills add VibiumDev/vibium --skill vibe-checkgit 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/vibe-check)<a href="https://agentmods.dev/skills/vibiumdev/vibium/vibe-check"><img src="https://agentmods.dev/badge/skills/vibiumdev/vibium/vibe-check.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.00037 | $0.04572 |
| Opus 5 | $0.00018 | $0.02286 |
| Sonnet 5 | $0.00007 | $0.00914 |
| Haiku 4.5 | $0.00004 | $0.00457 |
Grade A, and why
vibe-check 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 today.
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 — 404 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).
vibium go <url> && vibium map && vibium click @e1 && vibium map
Core Workflow
Every browser automation follows 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.
Command Chaining
Chain commands with && to run them sequentially. The chain stops on first error:
vibium go https://example.com && vibium map && vibium click @e3 && vibium diff map
When to chain: Use && for sequences that should happen back-to-back (navigate → interact → verify). Run commands separately when you need to inspect output between steps.
When NOT to chain: Don't chain commands that depend on parsing the previous output (e.g. reading map output to decide what to click). Run those separately so you can analyze the result first.
Commands
Discovery
vibium map— map interactive elements with @refs (recommended before interacting)vibium map --selector "nav"— scope map to elements within a CSS subtreevibium diff map— compare current vs last map (see what changed)
Navigation
vibium go <url>— go to a pagevibium back— go back in historyvibium forward— go forward in historyvibium reload— reload the current pagevibium url— print current URLvibium title— print page title
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.
- today Changed · +9 lines 3b278b545a1a
- yesterday Changed 901e552923e4
- 5d ago First seen · 395 lines · 37 tokens per session scan A 95c4171ba89d
vibe-check is a skill published in the GitHub repository VibiumDev/vibium (2,929 stars, last pushed today), licensed Apache-2.0. It adds 37 tokens to every session and 4,572 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-08-30.
Other skills, from other repositories
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
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.
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…
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
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.