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/Quindart-com/opencode-chromiumWrote 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/mcp/quindart-com/opencode-chromium/opencode-browser-plugin)<a href="https://agentmods.dev/mcp/quindart-com/opencode-chromium/opencode-browser-plugin"><img src="https://agentmods.dev/badge/mcp/quindart-com/opencode-chromium/opencode-browser-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/mcp/quindart-com/opencode-chromium/opencode-browser-plugin"><img src="https://agentmods.dev/badge/mcp/quindart-com/opencode-chromium/opencode-browser-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
opencode-browser-plugin 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 3d 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
{
"opencode-browser-plugin": {
"command": "npx",
"args": [
"-y",
"--package",
"[email protected]",
"opencode-chromium-mcp"
]
}
}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.
- 3d ago First seen · 11 lines scan A a6af7de2dd98
opencode-browser-plugin is an MCP server published in the GitHub repository Quindart-com/opencode-chromium (20 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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-10-13.
Other mcp servers, from other repositories
opencode-browser-mcp
Session-isolated browser automation over MCP and Chrome DevTools Protocol. Runs locally from the @mirsella/opencode-browser-mcp npm package.
cloakbrowser-mcp
Playwright MCP-compatible browser automation bridge for CloakBrowser Chromium. Runs locally from the cloakbrowser-mcp npm package. Needs 10 environment variables to run.
mcp
Lightweight browser automation for AI agents: navigate, screenshot, extract, PDF. One small binary. Runs locally from the @kitewright/mcp npm package.
fortress
Open stealth-browser framework — drive a real recompiled-Chromium (Fortress) that defeats bot-detection fingerprint suites. Drop-in stealth for browser-use, Playwright, Crawl4AI, with an MCP server for AI agents. Runs locally from the tilion Python package. Needs 5 environment variables to run.
drisp-browser-dev
MCP server "drisp-browser-dev" as configured in drisplabs/browser-mcp. Runs dist/src/index.js with node.
wavexis-mcp
MCP server exposing the wavexis browser automation library to LLMs — 220 tools, 13 capability tiers, zero Node.js. Runs locally from the wavexis-mcp Python package.