bitwarden-browser-aac-login

Installation
SKILL.md

Bitwarden Browser AAC Login

Contract

Use Agent Access only as an approved, domain-scoped credential handoff.

  • Never ask the user to paste passwords, TOTP codes, API keys, cookies, session values, rendezvous codes, or full credential JSON.
  • Never run commands that print AAC_USERNAME, AAC_PASSWORD, AAC_TOTP, environment dumps, shell history, cookies, or auth-capable files.
  • Treat aac run --env-all as sensitive: credentials are available to the child process and any code path that receives them.
  • Prefer a credential-blind helper that uses credentials without exposing them to the agent. If the practical path routes credentials through agent-controlled code in memory, say that clearly before use.
  • Confirm the exact target domain before requesting real credentials. Approve only the domain the user expects.
  • Stop before account creation, final submission, payment, permission grants, or sensitive form submission unless the user confirms at action-time.

Workflow

  1. Verify local prerequisites without reading secrets:
Installs
2
First Seen
Jun 4, 2026
bitwarden-browser-aac-login — arthurzakirov/agentdesk