setup-agent-sign-in

Installation
SKILL.md

Set up agent sign-in

Agents sign in as test users through agent-browser's local vault. The user saves each login once per machine from their own terminal, so the password moves from their clipboard into the vault and stays out of the conversation, command arguments and script output. The project's login script signs a session in with agent-browser auth login, and its sign-in doc tells agents which role covers which case.

Name each saved login <project>-<role>: a short project slug and the app's own role name in kebab case, such as fysioscout-clinic-admin.

Keep the password in the vault

These rules hold in every step, for the scripts and for you:

  • The password reaches agent-browser only through --password-stdin, in a command the user runs in their own terminal. Ask for emails, URLs and roles in chat; the user types the password nowhere else.
  • Read a saved login with agent-browser auth show, which prints its username and no password. Reach the vault only through agent-browser auth commands, leaving the files under ~/.agent-browser/ unread.
  • Scripts send the output of auth save and auth login to /dev/null and print their own one-line result.
  • On a login request, read only the status that network requests lists. Its detail view, a HAR recording, and an eval or get value on the password field expose the password, so sign-in uses none of them.
  • A window handed to Computer Use gets a fresh profile with Chrome's password manager off, so no save-password prompt can show the password.

These rules keep the password out of transcripts and logs. The vault's key is readable by the user's own account, so tell the user they protect against accidents, not against an agent that sets out to decrypt the vault.

Steps

Installs
62
GitHub Stars
1
First Seen
Oct 29, 2026