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.
npx skills add Brainrot-Creations/claude-plugins --skill agent-browsergit clone --depth 1 https://github.com/Brainrot-Creations/claude-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/skills/brainrot-creations/claude-plugins/agent-browser)<a href="https://agentmods.dev/skills/brainrot-creations/claude-plugins/agent-browser"><img src="https://agentmods.dev/badge/skills/brainrot-creations/claude-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/skills/brainrot-creations/claude-plugins/agent-browser"><img src="https://agentmods.dev/badge/skills/brainrot-creations/claude-plugins/agent-browser.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00108 | $0.01815 |
| Opus 5.5 | $0.00043 | $0.00726 |
| Sonnet 5.5 | $0.00022 | $0.00363 |
| Haiku 4.5 | $0.00011 | $0.00181 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- agent-browser — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser Automation with agent-browser
The CLI uses Chrome/Chromium via CDP directly. Install via npm i -g agent-browser, brew install agent-browser, or cargo install agent-browser. Run agent-browser install to download Chrome. Existing Chrome, Brave, Playwright, and Puppeteer installations are detected automatically. Run agent-browser upgrade to update to the latest version.
Hive Integration
Always use Hive before interacting with any webpage element. Hive is a collective intelligence layer — it stores proven selectors and interaction methods contributed by all agents. Using it means you start with what already works instead of discovering from scratch every time.
Before every interaction
- Extract the domain from the current URL (e.g. "github.com", "reddit.com").
- Define a clear
action_key(e.g. "click_submit_button", "fill_search_input", "click_reply"). - Call
hive_pullwith the domain and action_key. - If blocks are returned, try them top-down by rank:
type: "css"→ use as a CSS selector with agent-browsertype: "xpath"→ use as an XPathtype: "aria"→ use as an ARIA labeltype: "visual"→ use the description for screenshot-based targeting (screenshot --annotate)
- After each attempt, call
hive_vote— "up" if it worked, "down" if it failed, then try the next. - If all blocks fail or none exist, discover the method yourself (snapshot, screenshot, DOM), then call
hive_contributewith what worked.
After discovering a new method
Once you successfully interact with an element by your own discovery:
- Note the domain and action_key.
- Identify what worked: CSS selector, XPath, ARIA label, or visual description.
- If you tried a Hive block that failed before finding this, pass its block ID as
parent. - Call
hive_contributeso every future agent benefits.
If Hive is not available
If hive_pull, hive_contribute, or hive_vote are not available as tools, Hive is not enabled. Let the user know:
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 · 194 lines · 108 tokens per session scan A e3653adf12c4
agent-browser is a skill published in the GitHub repository Brainrot-Creations/claude-plugins (23 stars, last pushed 3mo ago), licensed MIT. It adds 108 tokens to every session and 1,815 once invoked, about $0.0004 per session on Opus 5.5. 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 skills, from other repositories
proof-e2e
Build E2E test specs for critical user journeys — Playwright or Cypress, page objects, setup/teardown, CI config. Use when asked to "write E2E tests", "end-to-end testing", "browser tests", "UI tests", or "Playwright tests".
e2e-panther-playwright
Write end-to-end tests with Symfony Panther 2.4 for browser automation or Playwright for complex scenarios.
playwright-qa
Driver P of orc:browser-qa — browser QA with Playwright Test and the stock planner/generator/healer agents against a resolved QA target; yields a stitched step-tagged video, traces, and qa-manifest.json.
browser-qa
The canonical browser-QA protocol for web changes — target resolution, env attach, the driver gate (Playwright primary, agent-browser, Claude-in-Chrome), validator dispatch, chrome evidence packet.
qa-targets
Resolve WHERE browser QA runs — named targets in .orc/targets.json (local, staging, preview), the Target gate, credential references (literal | op:// | env:), guard rule.
agent-browser
Browser automation CLI for AI agents; use for web tasks - navigate, click, fill forms, screenshot, scrape, test web/Electron apps.