sensitive-browser_skill

Overview

This skill executes sensitive browser actions—logins, payments, and form filling—outside the agent’s core loop using a dedicated CLI subprocess. It isolates credentials and payment data so authenticated browser workflows run with reduced exposure in the main agent context. Use it to perform authenticated actions and hand back session state for continued automation.

How this skill works

You supply a JSON file containing only the required sensitive fields and invoke the CLI with a natural-language task and target URL. The tool loads an optional Playwright storage state, runs the requested action in an isolated subprocess, updates the session state, and writes the new state to disk. The tool never prints secret values; it only indicates which fields will be used.

When to use it

• User requests login to a website with credentials
• Filling payment details or completing a checkout flow
• Submitting forms containing personal or sensitive data
• When browser automation needs an authenticated session handoff

Best practices

• Provide only the minimum required fields in the sensitive JSON and delete the file after use
• Use environment variables or a secret manager in production instead of on-disk files
• Pass and store Playwright storage state files securely and limit access
• Review which schema fields the tool intends to use before execution

Example use cases

• Log into a web app using a username and password and return an authenticated session state
• Fill a checkout page with card number, expiry, and CVV to complete a purchase flow (human-reviewed)
• Populate address and personal fields for a government or healthcare form submission
• Hand off session state from an unauthenticated agent-browser flow to sensitive-browser for authentication, then resume the agent