browser-login

Automates browser authentication and vaults sanitized session cookies for reuse.

70.1k|8.4k|Updated Jun 2, 2025
One-click install
npx skills add https://github.com/ruvnet/claude-flow --skill browser-login
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-login
Source: https://github.com/ruvnet/claude-flow/tree/main/plugins/ruflo-browser/skills/browser-login
Command: npx skills add https://github.com/ruvnet/claude-flow --skill browser-login

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Repeatedly driving login flows for the same host wastes time and risks exposing raw credentials and cookies in agent memory. This Skill authenticates once, sanitizes cookies through AIDefence, and stores an opaque vault handle in AgentDB so downstream browser skills can reuse the session.

Core Features & Use Cases

  • One-Time Auth Flow: Drives the login form with browser_fill and browser_type, including optional MFA handling, without reading credentials from .env files.
  • Cookie Sanitization: Passes each captured cookie through aidefence_scan to flag raw secrets and high-entropy tokens before storage.
  • Vaulted Session Reuse: Stores an opaque vault handle with expiry in the browser-cookies AgentDB namespace so skills like browser-extract and browser-form-fill can mount the session later.
  • Use Case: An agent that must scrape an internal dashboard daily logs in once with MFA, vaults the cookie handle, and subsequent runs mount the vaulted session instead of re-authenticating.

Quick Start

Ask the agent to log in to your target site with the browser-login skill, providing the login URL and an optional vault handle name, then reuse the returned handle for later browser sessions.

Frequently Asked Questions about browser-login

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reuse browser session cookies across agent runs?

Run the login flow once, capture cookies via browser_eval, sanitize them with aidefence_scan, and store an opaque vault handle in the browser-cookies AgentDB namespace. Downstream skills mount the vaulted handle instead of re-authenticating.

How to handle MFA during automated browser login?

Pass the --mfa flag to pause for user input or invoke the user's TOTP helper during the auth flow. The skill captures only the resulting redirect, never the MFA code itself.

Does this skill store raw passwords or cookie values?

No. Raw cookie values and tokens are vault-wrapped into opaque handles after AIDefence scanning, and trajectory steps record only form field names with redacted placeholders. Credentials are never read from .env files.

Why does a vaulted cookie fail when reused on a site?

Some sites bind cookies to a user-agent fingerprint, causing vaulted cookies to fail on reuse. The recommended fix is to re-run the login flow rather than attempting to fingerprint-match.

Is browser-login a credential storage solution?

No. The vault-handle pattern protects against AgentDB leaks but not against compromise of the agent's environment. It is designed for session reuse, not long-term credential management.