autonomous-ai-agency: Skill for Claude Code

Skill: dev-browser — Browser Automation via Sandboxed JS

Installation

npm install -g dev-browser
dev-browser install          # Downloads Playwright + Chromium

Add to .claude/settings.json to pre-approve all commands:

{"permissions": {"allow": ["Bash(dev-browser *)"]}}

Primary invocation styles

# Inline heredoc (most common)
dev-browser <<'EOF'
  const page = await browser.getPage("main");
  await page.goto("https://example.com");
  console.log(await page.title());
EOF

# Run a .js file
dev-browser run script.js

# Named browser instance (persists across runs)
dev-browser --browser my-project < script.js

# Connect to existing Chrome (local debugging port)
dev-browser --connect http://localhost:9222 <<'EOF'
  const page = await browser.getPage("main");
  await page.goto("https://example.com");
EOF

# Auto-discover Chrome with remote debugging enabled
dev-browser --connect <<'EOF'
  const page = await browser.getPage("main");
  console.log(await page.title());
EOF

CLI flags

Subcommands

dev-browser run FILE      # Run a JS file
dev-browser install       # Install Playwright browsers (Chromium)
dev-browser browsers      # List all managed browser instances
dev-browser status        # Show daemon status
dev-browser stop          # Stop daemon and all browsers

Sandbox environment

Scripts run in QuickJS WASM, NOT Node.js. These are NOT available:

• require() / import() — no module loading
• process — no process access
• fs / path / os — no direct filesystem access
• fetch / WebSocket — no direct network access
• __dirname / __filename — no path globals