Agent Browser

Before installing or using this skill, consider that: 1) the documentation instructs the agent to import and reuse browser sessions and save state files that can contain session tokens in plaintext — treat those files like passwords (encrypt them, .gitignore, delete when done). 2) The skill's metadata does not declare the env vars the templates use (APP_USERNAME, APP_PASSWORD, AGENT_BROWSER_ENCRYPTION_KEY, proxy creds). That mismatch means you should not assume the registry metadata fully describes the skill's sensitive requirements. 3) Using --auto-connect / Chrome --remote-debugging-port exposes full browser control to local processes — do not connect to a browser where you are logged into sensitive accounts. Prefer ephemeral profiles or the provided auth vault pattern rather than importing an already-authenticated browser. 4) If you need to run this, run it in a restricted environment (dedicated testing user/profile or VM/container), avoid connecting to your personal browser, set an encryption key for saved state, and delete state files after use. 5) Ask the publisher (or request updated metadata) to: declare required env vars/primary credential, document exactly where state is stored, and confirm whether the skill transmits any saved state off-host. Those clarifications would change this assessment to less suspicious.