Tap

AI browser automation protocol — run pre-built skills for 41 sites, or forge new ones. MCP native, deterministic, zero AI at runtime.

This tool is coherent for browser automation but comes with real privileges: the Chrome extension's debugger permission lets Tap read and control active tabs (including logged-in accounts), and 'tap install' can bring in and run community JavaScript stored under ~/.tap. Before installing: (1) inspect the GitHub repo, the Homebrew formula, and the extension manifest and source to confirm the debugger usage and no hidden permissions; (2) review community taps before running them; (3) if possible run Tap in an isolated browser/profile without sensitive logins or sync enabled; (4) prefer building from source after auditing code or verifying the release build provenance in CI; (5) avoid enabling autonomous invocation unless you accept that an agent could drive your browser using your active sessions. Proceed only if you are comfortable with those risks or can sandbox the browser environment.

Type: OpenClaw Skill Name: tap Version: 0.1.2 The 'tap' skill bundle provides extensive browser automation capabilities, including direct page manipulation (typing, clicking) and network requests via a Chrome extension requiring high-privilege 'debugger' permissions. A significant risk is identified in SKILL.md, which describes a 'tap install' command that fetches and executes external JavaScript 'skills' from a remote GitHub repository (LeonTing1010/tap-skills), creating a supply chain/RCE vector. While these capabilities are aligned with the stated purpose of deterministic automation, the combination of broad browser control and remote script execution is inherently high-risk.