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 ninnettesudanese653/claude-plugins --skill agent-browsergit clone --depth 1 https://github.com/ninnettesudanese653/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/ninnettesudanese653/claude-plugins/agent-browser)<a href="https://agentmods.dev/skills/ninnettesudanese653/claude-plugins/agent-browser"><img src="https://agentmods.dev/badge/skills/ninnettesudanese653/claude-plugins/agent-browser.svg" alt="Measured on agentmods" 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 | $0.00054 | $0.00907 |
| Sonnet 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 7d 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.
This is a copy
100% identical to agent-browser — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 7d ago First seen · 194 lines · 108 tokens per session scan A e3653adf12c4
agent-browser is a skill published in the GitHub repository ninnettesudanese653/claude-plugins (1 stars, last pushed 2d ago), licensed MIT. It adds 108 tokens to every session and 1,815 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agent-browser, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
hive.browser-automation
Required before any hive-browser CLI command. The browser is driven from the terminal by running hive-browser ... --json via terminalexec — not via MCP tools. Teaches the browser lifecycle rules (the bridge attaches to the USER'S running Chrome — never kill or launch browser processes; timeouts are transport issues…
hive.linkedin-automation
Read before automating LinkedIn with browser tools. LinkedIn combines shadow DOM (#interop-outlet), strict Trusted Types CSP that silently drops innerHTML, Lexical composer, native beforeunload dialogs that hang the bridge, and aggressive spam filters — each has bitten us at least once. Verified flows for profile…
hive.x-automation
Read before automating X / Twitter with browser tools. Verified flows for post, reply, delete, search-and-engage, plus the Draft.js compose quirks that silently disable the send button. Includes the daily-reply and job-market-reply playbooks. Requires hive.browser-automation for the underlying screenshot + coordinate…
hive.slack-notifications-setup
Set up a Slack notification channel (Sentinel) for a colony by driving the browser — reuse or create the "Hive Sentinel" Slack app from a JSON manifest, install it, capture the bot + app tokens, create/select the channel via the Slack API, and turn Sentinel on so the colony can ping the user on Slack and accept…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
shogun-screenshot
A screenshot tool for getting images from a computer or web page and then cropping, resizing, or masking sensitive information. Playwright is a browser-automation tool used here to capture web pages.