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 coelhobugado/antigravity-browser-bridgenpx agentmods add plugins/coelhobugado/antigravity-browser-bridge/agent-browsergit clone --depth 1 https://github.com/coelhobugado/antigravity-browser-bridgeWrote 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/coelhobugado/antigravity-browser-bridge/agent-browser)<a href="https://agentmods.dev/plugins/coelhobugado/antigravity-browser-bridge/agent-browser"><img src="https://agentmods.dev/badge/plugins/coelhobugado/antigravity-browser-bridge/agent-browser.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
agent-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 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.
What it actually says
{
"name": "agent-browser",
"description": "Automates browser interactions for web testing, form filling, screenshots, and data extraction",
"source": "./",
"strict": false,
"skills": [
"./skills/agent-browser"
],
"category": "development"
}What ships with it
1 file beside marketplace.json#agent-browser in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 10 lines scan A 707e1a8e66d7
agent-browser is a plugin published in the GitHub repository coelhobugado/antigravity-browser-bridge (1 stars, last pushed 1mo 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-09-03.
Other plugins, from other repositories
playwright-rust
Procedural reference for writing Rust browser automation with playwright-rs: adding the crate and installing its browsers, object model, the locator!() macro, builder options, auto-wait semantics, and trace capture.
browser-relay
Let agents use the Chrome you already have open and logged in through a Skill + CLI, locally or across machines.
byob
Control the user's real Chrome from Claude Code through a local, auditable bridge.
chromeboost
Drive your real Chrome from Claude Code — movable/hideable HUD plus occlusion-aware cursor control that clicks through JS overlays, scrims and sticky bars. Bundles the ChromeBoost MCP server, permission allowlist, and usage skill.
mochi
A browser companion for AI assistants. Bundled MCP tools for Chrome automation, persistent project memory (Continuum chain), and an in-page hint modal — pair with the Mochi Chrome extension.
chromeflow
Let Claude Code drive your real browser — clicks, fills forms, grabs API keys, writes them to .env. Bundles the chromeflow MCP server, permission allowlist, and usage skill.