Agb

This skill appears to do what it says (automated browser interactions), but review these before installing: 1) The index.js calls a hardcoded binary path (/root/.local/bin/agent-browser) — confirm the expected agent-browser binary is present and trusted in your environment to avoid a replaced binary being executed. 2) The tool encourages saving session state files (auth-state.json) and using environment variables for credentials; treat those files and env vars as secrets, never commit them to source control, and remove them when done. 3) Proxy examples show credentials in proxy URLs — avoid embedding secrets in URLs or logs; prefer secure storage and runtime injection of credentials. 4) The scripts call pkill -f chromium and recommend ignoring HTTPS errors in some debugging examples — be cautious running these commands in multi-tenant or production environments. 5) Because the skill automates login flows and can replay sessions, only use it with accounts and sites you control or for which you have permission. If you need higher assurance, ask the author for: (a) confirmation of the expected agent-browser binary path on your platform, (b) a signed/official release link for agent-browser, and (c) a minimal example run that shows no unexpected network endpoints or exfiltration.