passwordstore-broker
por bieggerm
DevOps & CloudResumen
Enforce safe secret handling by collecting secrets through one-time HTTPS forms, storing them in pass.
Descripción
Qué hace esta skill
Manages credential handling for AI agents by collecting secrets through one-time local HTTPS forms and storing them in pass (passwordstore). Commands run with secrets injected as environment variables via a wrapper script. Raw values never appear in chat context, logs, or commit history.
Unlike passing secrets inline or via dotenv files, collection and injection happen entirely through dedicated scripts, so raw values never touch chat transcripts, command logs, or repo files.
Cuándo usarla
- Providing an API key to an agent without typing it in chat
- Storing AWS credentials for automated deployment scripts
- Collecting a secret from a phone over LAN with TOTP verification
- Rotating a service token in the local vault without re-exposing it
- Running authenticated CLI tools without leaking credentials into shell history
Flujo de trabajo de ejemplo
User asks: Run a script that needs my OpenAI API key
- 1
Check vault: scripts/vault.sh exists openai/prod/api_key
- 2
Secret missing, launch intake form: scripts/get_password_from_user.py --secretname openai/prod/api_key --port 8443
- 3
Send generated HTTPS URL to user; user submits key via browser form
- 4
Confirm secret is now stored in vault
- 5
Execute command: scripts/run_with_secret.sh --secret openai/prod/api_key --env OPENAI_API_KEY -- python3 my_script.py
Script runs with OPENAI_API_KEY injected; secret never appears in chat or logs
Requisitos
- pass (Unix password manager) installed and initialized with a GPG key
- gpg key pair configured for pass encryption
- qrencode installed (for TOTP QR code generation in LAN mode)
- TOTP authenticator app on phone (required for LAN mode secret intake)
Instalación
clawhub install bieggerm/passwordstore-brokerEjecuta el comando de la CLI o pega el prompt en Claude Code, Cursor, Codex o el agente de programación que uses.