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.
git clone --depth 1 https://github.com/frane/vibesurferWrote 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/plugins/frane/vibesurfer/plugin)<a href="https://agentmods.dev/plugins/frane/vibesurfer/plugin"><img src="https://agentmods.dev/badge/plugins/frane/vibesurfer/plugin/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/plugins/frane/vibesurfer/plugin"><img src="https://agentmods.dev/badge/plugins/frane/vibesurfer/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade 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 1mo 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.
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 it installs
The manifest is a name and a version. 2 skills, 1 MCP server travel with it, and installing the plugin installs all of them — 135 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 14 lines scan A f16b4599e505
vibesurfer is a plugin published in the GitHub repository frane/vibesurfer (16 stars, last pushed 22d 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
assay
Opens a page you changed, drives every control it offers, and reports what it did and what happened. One line every time, clean or not.
webcmd
Self-learning browser infrastructure for AI agents: live browser control plus local sitemap memory that makes repeat runs faster and cheaper.
only-cli marketplace
Plugin marketplace listing 1 plugin: only-cli.
only-cli
Browse websites from the terminal in a few hundred tokens.
tauri-mcp-cli
Exposes Tauri MCP skills that can be used to control the webview of a running Tauri app from an AI assistant.
tauri-mcp
Agent Skills for automating and testing Tauri v2 applications.