browser-automation

BENIGN for stated purpose, but high-impact. The skill is internally consistent and uses an official npm-distributed browser automation CLI, not an obvious credential-harvesting proxy. The main risk is operational: it grants an agent broad browser powers over arbitrary web content, including login/session handling, form submission, downloads, and page-script evaluation, with most safety controls disabled by default.