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/pleaseai/claude-code-pluginsWrote 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/pleaseai/claude-code-plugins/agent-browser)<a href="https://agentmods.dev/plugins/pleaseai/claude-code-plugins/agent-browser"><img src="https://agentmods.dev/badge/plugins/pleaseai/claude-code-plugins/agent-browser/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/pleaseai/claude-code-plugins/agent-browser"><img src="https://agentmods.dev/badge/plugins/pleaseai/claude-code-plugins/agent-browser.svg" alt="Reviewed on agentmods" width="80" 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 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": "agent-browser",
"version": "1.3.1",
"description": "Browser and desktop app automation for AI agents — web browsing, Electron app control, Slack automation, and QA testing workflows",
"author": {
"name": "Vercel Labs",
"url": "https://github.com/vercel-labs"
},
"repository": "https://github.com/vercel-labs/agent-browser",
"license": "Apache-2.0",
"keywords": [
"agent-browser",
"browser",
"automation",
"agents"
],
"skills": "./.agents/skills/"
}
What it installs
The manifest is a name and a version. 4 skills travel with it, and installing the plugin installs all of them — 500 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 Changed caa9a383ff84
- 1mo ago First seen · 19 lines scan A 0b6b631c43b8
agent-browser is a plugin published in the GitHub repository pleaseai/claude-code-plugins (16 stars, last pushed 5d ago), licensed MIT. 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
sap-sac-test-automation
SAP Analytics Cloud (SAC) automated testing skill for designing capability-gated browser discovery and deterministic Playwright test suites for SAC stories, dashboards, reports, planning workflows, comments, permissions, visual regression, and reusable QA automation. This skill should be used when building SAC…
sniff
Autonomous QA scanner via sniff-qa: walks your running app in a real browser and reports real bugs (broken pages/links, console/network errors, broken forms, state-loss, empty/placeholder data, bad loading/error states, responsive + a11y) with reproduction proof, severity, confidence, and a fix. No API key.
headless
Headless browser automation for site comparison, E2E testing, and anti-bot-aware web research.
e2e-runner
JSON-driven E2E browser test runner — no JavaScript test files needed. Parallel execution against a Chrome pool (browserless, CDP, Lightpanda, Obscura, Steel), 28+ built-in actions, visual verification, network debugging, flaky test detection, reusable modules, and a real-time dashboard. Includes 3 specialized agents.
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction.
user-testing-agent
Persona-based user testing agent that simulates realistic user interactions with web applications. Embodies different user archetypes (Boomers, Millennials, Gen Z, Gen Alpha) with authentic behaviors, timing patterns, and frustration triggers to identify UX issues before real users do.