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/MadAppGang/magusWrote 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/madappgang/magus/browser-use)<a href="https://agentmods.dev/plugins/madappgang/magus/browser-use"><img src="https://agentmods.dev/badge/plugins/madappgang/magus/browser-use/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/madappgang/magus/browser-use"><img src="https://agentmods.dev/badge/plugins/madappgang/magus/browser-use.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "browser-use",
"version": "1.9.1",
"description": "Full-platform browser automation: live-page JS eval, keyboard and focus primitives, file screenshots, preflight and a configurable agent LLM, on local or cloud browsers. Runs Playwright's own Chromium, never your real Chrome. Adds Magus tools and 6 skills to the upstream Browser Use MCP set.",
"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",
"mcpServers": "./.mcp.json",
"skills": [
"./skills/core-api",
"./skills/navigation-patterns",
"./skills/web-scraping",
"./skills/debug-ui",
"./skills/hybrid-debugging",
"./skills/agent-model"
],
"requires": {
"schema": 1,
"bin": [
{
"name": "bun",
"check": [
"bun",
"--version"
],
"install": [
{
"via": "bootstrap",
"tool": "bun"
}
]
},
{
"name": "uv",
"check": [
"uv",
"--version"
],
"install": [
{
"via": "brew",
"os": [
"darwin"
],
"formula": "uv"
},
{
"via": "bootstrap",
"tool": "uv"
}
]
},
{
"name": "browser-use-env",
"check": [
"uv",
"run",
"--offline",
"--no-config",
"--script",
"${CLAUDE_PLUGIN_ROOT}/scripts/mcp-server.py",
"--check-env"
],
"install": [
{
"via": "uv-script",
"script": "scripts/mcp-server.py",
"args": [
"--check-env"
What it installs
The manifest is a name and a version. 6 skills, 1 hook travel with it, and installing the plugin installs all of them — 225 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.
- 11d ago Changed · +103 lines 508da0c84f73
- 21d ago Changed 9988041b06c7
- 23d ago Changed 7ef2d2ec5db1
- 29d ago Changed b797998c09ea
- 1mo ago Changed ea095c257a1f
- 1mo ago First seen · 42 lines scan A fa3bfcdcb3f0
browser-use is a plugin published in the GitHub repository MadAppGang/magus (13 stars, last pushed 2d 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.
Other plugins, from other repositories
build-information
MCP configuration declaring 1 server: build-information.
kernel-sdks
TypeScript and Python SDK skills for building browser automation with Kernel's Typescript and Python SDKs.
realbrowser
Target-first local Chrome/Chromium browser control with signed-in profiles, labeled tabs, and guarded actions.
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.
rad-chrome-extension
MV3 Chrome extension development standards (WXT, React, TypeScript) with two pure-stdlib Python validators that catch what LLM eyeballing misses. Skills cover architecture, MV3 security (CSP, remote code ban, content script isolation), permission minimization and CWS compliance, typed messaging, storage selection…
headless
Headless browser automation for site comparison, E2E testing, and anti-bot-aware web research.