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 agentmods add skills/jmagly/aiwg/browser-setupnpx skills add jmagly/aiwg --skill browser-setupgit clone --depth 1 https://github.com/jmagly/aiwgWrote 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/jmagly/aiwg/browser-setup)<a href="https://agentmods.dev/skills/jmagly/aiwg/browser-setup"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/browser-setup.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.00069 | $0.01609 |
| Opus 5 | $0.00034 | $0.00805 |
| Sonnet 5 | $0.00014 | $0.00322 |
| Haiku 4.5 | $0.00007 | $0.00161 |
Grade B, and why
browser-setup scanned grade B with 1 finding 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 yesterday.
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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
chmod 700 ~/.config/playwright-mcp How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser Setup Skill (DRAFT)
Status: DRAFT — scaffolded from PoC. Implementation pending Inception outputs.
Purpose
End-to-end interactive wizard that takes a user from "AIWG agent can't drive a browser" to "AIWG agent is connected to my real, logged-in browser via the Playwright MCP Bridge extension" without the user needing to know the underlying MCP plumbing, token semantics, or AIWG CLI surface.
When This Skill Applies
- User asks the agent to "open a website" or "log into X for me" and AIWG detects no browser MCP is configured
- User explicitly requests browser-control setup
browser-doctorreports the addon is installed but unwired
Inputs
| Field | Source | Notes |
|---|---|---|
| Provider | aiwg runtime-info |
Auto-detect; user can override |
| Target browser | OS-specific detection | Recommend based on --extension support |
| Token | Interactive (AskUserQuestion) | Pasted by user after installing extension |
Walkthrough (planned)
Step 1: Pre-flight
Confirm AIWG is initialized in the workspace and the active provider supports MCP servers with env blocks. Bail with explicit guidance if not.
Step 2: Detect installed browsers
Linux:
which google-chrome google-chrome-stable microsoft-edge microsoft-edge-stable chromium chromium-browser brave-browser vivaldi operaflatpak list --app 2>/dev/null | grep -iE 'chrome|chromium|edge|brave|vivaldi'
macOS:
mdfind 'kMDItemContentType == "com.apple.application-bundle"'filtered by known bundle IDs (com.google.Chrome,com.microsoft.edgemac,org.chromium.Chromium,com.brave.Browser)
Windows:
- Read
HKLM\SOFTWARE\Clients\StartMenuInternet\and standard install paths
Classify each detected browser by extension-mode support:
- Native extension support: Chrome, Edge
- CDP fallback only: Chromium, Brave, Vivaldi, Arc, Opera
Step 3: Recommend a browser
Present detected browsers ranked by:
- Already installed AND supports
--extension - Already installed but needs CDP fallback (note caveats)
- Not installed (provide install URL but don't auto-install)
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.
- yesterday First seen · 168 lines · 69 tokens per session scan B 28ca0e204cff
browser-setup is a skill published in the GitHub repository jmagly/aiwg (209 stars, last pushed today), licensed MIT. It adds 69 tokens to every session and 1,609 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other skills, from other repositories
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
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…
browser_visible
以可见模式启动真实浏览器窗口，适用于演示、调试或需要人工参与的场景。控制 headed/cdpPort 等启动参数。.
browser-cdp
Native CDP browser automation reference. Headless/headed Chrome control, screenshots, JS evaluation. (/browser-cdp, browser automation, cdp, scraping).
agent-browser
Headless browser automation CLI. Open, browse, interact with, and screenshot web pages. Use when: opening websites, browser-based login, web app testing, taking screenshots, UI verification.
skeptical-triage
Reusable 3-round self-challenge + arbiter pattern for filtering false positives from findings/verdicts. Use when the cost of a false-positive gate block exceeds the cost of 4 extra LLM turns.