Browser Automation

Do not install or run the npm commands from this package yet. Key concerns: (1) The package metadata claims no required env vars or binaries, but the docs and setup.json require ANTHROPIC_API_KEY, optional Browserbase API keys, Chrome, and npm dependencies — this inconsistency suggests the published bundle is incomplete or mislabeled. (2) The tool preserves a Chrome profile and saves downloads locally (./agent/downloads/), which can retain cookies, active sessions, and downloaded files — consider privacy implications. (3) Browserbase/remote mode would send browsing activity and page contents to a remote service if BROWSERBASE_* keys are present; the skill claims it will switch to that mode automatically without prompting. (4) The docs instruct running `npm install` and `npm link` for a global CLI but no source/package files are present in the bundle; running these commands from an unknown source could install arbitrary code. Before proceeding, ask the publisher for: (a) the source repository or a verified release tarball (ideally GitHub or official domain), (b) a package.json and full source to inspect, (c) corrected registry metadata that lists required env vars and permissions, and (d) details about what Browserbase is, its privacy policy, and where remote traffic is sent. If you must test: run in an isolated VM/container, do not reuse real browser profiles or credentials, and never expose real ANTHROPIC_API_KEY or other secrets until you have verified the code and origin.