Login Flow

Login Flow

When to invoke

The user task requires authentication. The agent provides credentials in:

• vars.username (or vars.email)
• vars.password

Per and [docs/ethics.md](../../docs/ethics.md): we use the agent-provided creds only — typically sourced by the agent from env vars ($SITE_X_USER, $SITE_X_PASS) the user has set, or from a password manager the user controls. We never harvest, prompt for, or store credentials. The sensitive: true metadata flag tells the trace recorder to redact form-fill events in the exported zip.

Recipe

1. waitfordom_ready timeout=5s
2. waitforselector selector="input[type='password']" state=visible timeout=5s
3. fill selector="input[type='email'], input[name='username'], input[name='email'], input[id='username'], input[id='email']" value="$vars.username"
4. fill selector="input[type='password']" value="$vars.password"
5. click selector="button[type='submit'], button:has-text('Sign in'), button:has-text('Log in'), input[type='submit']"
6. wait extra=1000ms

Success criteria

• assert novisibleelement selector="input[type='password']"
• assert urlchangedsince=step1 OR cookiesetnamed="session"

When NOT to use

• OAuth / SSO flows that redirect through identity providers

(Google, Microsoft, Okta). Use handle-oauth-redirect (v0.2.0).

• Magic-link / passwordless flows. Out of v1 scope; agent must

poll its inbox separately.

• MFA-protected logins. If MFA is enabled and there's no pre-saved

session, the recipe will hit the MFA challenge and stop. The agent surfaces the MFA prompt and asks the user how to proceed.

Known failures

• **Sites that hide the password field until the email is submitted

first** (Google-style): the recipe fills email, submits, then needs to re-find the password field. v0.1 fails on these; the agent can retry with a "submit, wait, re-invoke" loop.

• Captcha after a few failed attempts: detect-captcha should be

chained after this skill.

• "Are you sure?" dialogs post-login: handle-modal-dialog chains.

Trace handling

Per sensitive: true:

• form-fill events for password fields are recorded as `{value:

"[REDACTED]"}` in the trace

• screenshots taken during this skill's steps are blackened over the

password field's bounding box (v0.1 omits screenshots from this skill entirely)

Related skills

• dismiss-cookie-banner — sites with consent walls hit this first
• detect-captcha — failed-login rate-limiting often triggers captcha

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: bettyguo
• Source: bettyguo/browser-skills
• License: MIT

Install and usage instructions live in the source repository linked above.