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.
/plugin marketplace add frane/vibesurfernpx agentmods add plugins/frane/vibesurfer/plugingit clone --depth 1 https://github.com/frane/vibesurferGrade A, and why
vibesurfer 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 yesterday.
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.
What it actually says
{
"name": "vibesurfer",
"description": "Agent-native headless browser.",
"version": "0.2.0",
"author": {
"name": "Frane Bandov",
"url": "https://github.com/frane"
},
"homepage": "https://github.com/frane/vibesurfer",
"repository": "https://github.com/frane/vibesurfer",
"license": "Apache-2.0",
"keywords": ["browser", "headless", "webkit", "stateful", "mcp", "automation"]
}
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.
- yesterday First seen · 14 lines scan A f16b4599e505
vibesurfer is a plugin published in the GitHub repository frane/vibesurfer (15 stars, last pushed 5d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
yutori
macOS computer use, browser automation, deep research, and web monitoring (Scouts).
yutori-plugins
Plugin marketplace listing 1 plugin: yutori.
kaboom-workflows
Workflow commands that compose Kaboom MCP's 5 browser telemetry tools into complete, opinionated workflows for debugging, auditing, recording, and interactive development.
chrome-multi-instance-warn
An agent driving a browser tends to start a new one rather than use the one already open, and to size its work off the core count. This warns once per session when a tool payload is about to do either. Never blocks.
didvc-browser-plugins
Small, single-purpose Claude Code plugins focused on staying out of the machine's way.
browser-harness
Direct browser control via CDP. Drives the user's real Chrome (or a Browser Use cloud browser) with coordinate clicks, screenshots, and Python helpers — no selector hunting. Requires the one-time browser-harness CLI install (see the skill's references/install.md).