Run trusted local commands with 1Password secret references and suppressed output.

version
0.1.0
GitHub stars
436

Install

/plugin install onepassword-connector@grc-engineering-suite

Run it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.

Contents

Discovered from source

Skills 1

1Password connector

Point operators to /onepassword-connector:run. Never execute it from the agent, request credentials or read secret values. Explain that the helper suppresses output but cannot control a trusted program's own files or network activity. Use a dedicated, narrowly scoped 1Password service account where appropriate. For operator-only Document item consumption, point to /onepassword-connector:document; never retrieve document contents in the agent. These helpers are not findings collectors.

Commands 2

/onepassword-connector:document

Do not run this from Claude or any agent tool. Give instructions to the operator; never request or read document contents, credentials, or service-account tokens. In a trusted terminal, install 1Password CLI v2 and authenticate beforehand with its desktop integration or a narrowly scoped service account. The helper has no interactive stdin; biometric approval may require a graphical session.

Use the 26-character vault and Document item IDs, not their names:

node /path/to/onepassword-connector/scripts/document.js VAULT_ID DOCUMENT_ID -- /path/to/trusted-consumer --configured-option

The helper retrieves one Document item into memory (maximum 10 MiB) and passes its exact bytes to the trusted consumer's standard input, with no shell interpretation. It suppresses provider and consumer output. Exit 0 means success, 1 means retrieval or consumer failure, and 2 means invalid invocation. The consumer is not started after a failed or oversized retrieval. No live-provider authentication behavior has been verified here. The provider has a 2-minute deadline and the consumer a 5-minute deadline; the direct process is forcibly terminated on timeout. Descendants are not contained and can outlive the helper or keep inherited pipes open, delaying its return.

This is not a sandbox: the consumer can write, log, or transmit document contents. It inherits environment variables other than OP_-prefixed variables; credentials stored under other names may still reach it. Provider configuration and inherited loader variables can affect the processes. Memory or swap may be accessible to privileged local users. Protect the host, avoid secrets in arguments and logs, and choose the executable and its arguments yourself. The helper does not create a sanitized finding, discover metadata, or integrate automatically with evidence collection. Files attached to other item types are not supported.

/onepassword-connector:run

Do not run this command from Claude or any agent tool. Provide the operator the instructions below; never ask for, read, or print secret values or service tokens. This connector is an opt-in runtime-injection helper, not an evidence collector.

Install 1Password CLI v2 and authenticate outside the agent session using the vendor-supported desktop integration or a narrowly scoped service account. Its vault permissions should grant access only to needed items. This helper provides no interactive stdin, so sign in beforehand; desktop biometric approval may require a graphical session. It does not pass tokens in command arguments.

In a trusted terminal, set references (not values), then invoke a trusted command:

export CONNECTOR_TOKEN='op://MyVault/MyItem/credential'
node /path/to/onepassword-connector/scripts/run.js -- /path/to/trusted-collector --configured-option

The reference is an example; use a valid field reference for your item. The helper checks only that an allowed value starts with op://; it does not parse or validate reference syntax, completeness, existence, or access. 1Password CLI resolves and validates references; a prefix alone is not proof of a valid reference. See 1Password secret reference syntax. References are permitted only as values beginning with op:// in CONNECTOR_TOKEN, TOKEN, API_TOKEN, API_KEY, ACCESS_TOKEN, or PASSWORD; other variables containing op:// cause an error before op starts. This prevents resolving references into loader or interpreter control variables. Commands needing another variable name require a trusted adapter. op run scans the inherited environment. The helper does not fetch fields into the agent, write secret files or findings, or forward child stdout/stderr. Exit 0 means the child succeeded; 1 means provider or child failure; 2 means invalid invocation or no environment reference. Diagnostics are intentionally generic. Provider/child errors cannot be distinguished here.

Only run programs you trust: the child receives resolved secrets in its environment and can write, log, transmit, or disclose them. Other inherited environment variables, including service-account credentials, may also reach the child. A local process with sufficient privileges may inspect process memory or environment. Protect the terminal, host and CI logs; do not put secret values in arguments, shell history, tickets, findings, or agent conversations. Arguments are passed literally without a shell; pipes and redirects are not interpreted. The helper cannot control files or network calls made by the selected program. Use a secure collector that writes sanitized evidence itself. For Document items, see /onepassword-connector:document. Metadata discovery, finding generation, and automatic integration with collect-evidence are not implemented.

Sponsors

Details

Marketplace
GRCEngClub/claude-grc-engineering
Source
plugins/connectors/onepassword-connector
Category
Community

More from GRCEngClub/claude-grc-engineering

All 70