A browser-automation add-on built around Playwright's Chromium browser, with tools for interacting with and inspecting live web pages.

Use it to navigate pages, click and type, inspect the page structure, run JavaScript, extract content, take screenshots, and manage tabs.

It lets an agent work with web pages in a separate browser environment and supports tasks such as testing, scraping, and interface debugging.

browser-use — Plugin by MadAppGang

Install

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.

Claude Code

/plugin marketplace add MadAppGang/magus

agentmods

npx agentmods add plugins/madappgang/magus/browser-use

Clone the repo

git clone --depth 1 https://github.com/MadAppGang/magus

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

browser-use 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 2d 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.

plugins/browser-use/.claude-plugin/plugin.json · 42 lines

What it actually says

{
  "name": "browser-use",
  "version": "1.7.3",
  "description": "Full-platform browser automation. Live-page JS eval, keyboard and focus primitives, environment preflight, and a configurable agent LLM, across dual local and cloud browsers backed by Playwright's own Chromium so your real Chrome is never hijacked. Ten Magus-specific tools on top of the upstream Browser Use MCP set, plus 6 skills.",
  "author": {
    "name": "Jack Rudenko",
    "email": "[email protected]",
    "company": "MadAppGang"
  },
  "license": "MIT",
  "keywords": [
    "browser",
    "automation",
    "scraping",
    "testing",
    "accessibility",
    "browser-use",
    "cdp",
    "dom",
    "vision",
    "cloud",
    "captcha",
    "debugging"
  ],
  "category": "development",
  "setup": {
    "pip": [
      "browser-use",
      "mcp"
    ]
  },
  "mcpServers": "./.mcp.json",
  "skills": [
    "./skills/core-api",
    "./skills/navigation-patterns",
    "./skills/web-scraping",
    "./skills/debug-ui",
    "./skills/hybrid-debugging",
    "./skills/agent-model"
  ]
}

Changes

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.

2d ago First seen · 42 lines scan A fa3bfcdcb3f0

Subscribe to this mod's changes

browser-use is a plugin published in the GitHub repository MadAppGang/magus (9 stars, last pushed 4d 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-31.

Browser automation

browser-use

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other plugins, from other repositories

skills

handbook-qa

cli

kernel-sdks

claude-webcache

openlinker