credential-handofflisted

# Credential Handoff Bundled commands use `$PLUGIN_ROOT` (`$env:PLUGIN_ROOT` in PowerShell; same path suffix) for the plugin root. Set it once from the host's plugin-root variable when defined; otherwise use this skill folder's `../..`. Use this skill when work is blocked on a password, passphrase, OTP, API token, login, device unlock/trust action, Windows Hello approval, or a 1Password item. The agent may coordinate the handoff, but the secret value must not enter model context or an agent-observed tool result. Read `$PLUGIN_ROOT/references/credential-handoff-contract.md` before choosing a 1Password mode, a browser/device handoff, or a non-native input adapter. ## Required Route 1. Prove a credential is actually required with a non-prompting probe when the target supports one. Do not create an unexpected blocking prompt during discovery. 2. Choose the narrowest route: - native hidden prompt in a separate user-visible terminal; - `op run` or a 1Password Shell Plugin that injects only into the target subprocess; - direct user action in a browser, password-manager, system-authentication, or device-unlock surface that the agent must not automate. 3. Tell the user the target, purpose, expected input type and prompt count. Do not ask them to paste the value into chat or an ordinary text-input tool. 4. Observe only an allowlisted receipt such as `running`, `succeeded`, `failed`, or `cancelled`, plus a non-secret exit code. Never capture the de