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 MadAppGang/magus --skill browser-use-integrationgit 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/skills/madappgang/magus/browser-use-integration)<a href="https://agentmods.dev/skills/madappgang/magus/browser-use-integration"><img src="https://agentmods.dev/badge/skills/madappgang/magus/browser-use-integration/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/madappgang/magus/browser-use-integration"><img src="https://agentmods.dev/badge/skills/madappgang/magus/browser-use-integration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00039 | $0.01014 |
| Opus 5 | $0.00019 | $0.00507 |
| Sonnet 5 | $0.00008 | $0.00203 |
| Haiku 4.5 | $0.00004 | $0.00101 |
Grade A, and why
browser-use-integration 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 4d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser-Use Plugin Integration
Overview
The browser-use plugin provides headless Chromium screenshot capability as a fallback
when the claude-in-chrome extension is unavailable. When installed alongside designer,
it enables the design-review agent to capture browser screenshots without requiring
the user's Chrome instance to be open.
This skill is optional — all designer plugin functionality works without browser-use installed. browser-use is the fallback for Tier 2 of the three-tier browser capture chain:
- claude-in-chrome (preferred — real Chrome, CSS snapshot, JS execution)
- browser-use (fallback — headless Chromium, screenshot only)
- Error with install options
When to Use
Use this skill when:
- The
design-reviewagent has REFERENCE_TYPE = "browser" (URL reference) - The
design-reviewagent has IMPL_TYPE = "url" (URL implementation) - claude-in-chrome extension is NOT installed or unavailable
- User needs automated screenshot capture without opening Chrome manually
Detection Pattern
Probe the MCP tools directly — no subprocess, no plugin listing. A tool that answers is the only presence check this skill makes:
chrome_available = try mcp__claude-in-chrome__tabs_context_mcp()
→ success: use Tier 1 (claude-in-chrome)
→ error: chrome not available
browser_use_available = try mcp__browser-use__browser_list_sessions()
→ success: use Tier 2 (browser-use)
→ error: neither available → Tier 3 (error)
Screenshot Capture Pattern
When browser-use is available (Tier 2), use this exact sequence:
Step 1: Navigate (creates session automatically)
mcp__browser-use__browser_navigate(url: TARGET_URL)
→ save session_id from response
Step 2: Capture screenshot
mcp__browser-use__browser_screenshot(session_id: SESSION_ID, full_page: False)
→ returns: {"image": "<base64-PNG>", "format": "png", "width": N, "height": N}
→ save BASE64_DATA from response["image"]
Step 3: Decode base64 to file (Python3 is available when browser-use is installed)
Bash:
python3 -c "import base64, sys; open('${OUTPUT_DIR}/filename.png','wb').write(base64.b64decode(sys.argv[1]))" "${BASE64_DATA}"
Step 4: Verify file was created
Bash:
test -f "${OUTPUT_DIR}/filename.png" && echo "ok" || echo "decode_failed"
If decode_failed: close session then stop with error.
Step 5: Close session (ALWAYS — even on error)
mcp__browser-use__browser_close_session(session_id: SESSION_ID)
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.
- 4d ago Changed · -11 lines ce52a1aa45fd
- 8d ago First seen · 121 lines · 39 tokens per session scan A fcf20a089d66
browser-use-integration is a skill published in the GitHub repository MadAppGang/magus (9 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 1,014 once invoked, about $0.0002 per session on Opus 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-31.
Other skills, from other repositories
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
azure-messaging-webpubsub-java
Build real-time web applications with Azure Web PubSub SDK for Java. Use when implementing WebSocket-based messaging, live updates, chat applications, or server-to-client push notifications.
google-safe-browsing
Prevent and fix Google Safe Browsing "Dangerous site" flags. Use when launching a public web app, buying/picking a domain, building a login or signup page, or when any site shows a red "Dangerous site" / "Deceptive site" warning in Chrome, Brave, Safari, Firefox, or Edge. Triggers on "dangerous site", "deceptive…