onepassword-secretslisted

## Cross-cutting rules These rules apply to every operation in this skill without exception. - **Never print or restate a resolved secret value.** If a resolved value appears in output, treat it as compromised and rotate it immediately. - **Reference secrets only as `op://Vault/Item/field`** (or `op://Vault/Item/Section/field`). Never embed raw values in code, templates, or responses. - **Prefer `op run` over `op inject` over `op read`.** Each step down the hierarchy increases the risk that a resolved value reaches context or disk. - **`op item get --reveal` and `op item get` with `--format json` are as dangerous as `op read`**: they print resolved values and must be treated with the same caution. - **Always scope with `--vault`** to prevent accidental resolution against the wrong vault. - **The wrapped child in `op run -- <cmd>` is the real risk surface**: the child inherits all resolved environment variables. Network tools, shells, and interpreters can exfiltrate those values in a single approved call. - **Every `op` invocation requires explicit approval.** Never assume a prior approval covers a new call. Never run `op` speculatively. Never advise the user to select "always allow" for `op`. ## Setup & auth The `op` CLI must be installed, signed in (`op signin`), and connected to a 1Password account before any secret resolution is possible. Service account authentication uses the `OP_SERVICE_ACCOUNT_TOKEN` environment variable instead of an interactive session. Biometric