browser-aac-login
Installation
SKILL.md
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-allas 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 Codex. If the practical path routes credentials through Codex-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
- Verify local prerequisites without reading secrets: