1password

Read and inject credentials from the 1Password CLI into commands and templates.

Updated May 5, 2026
One-click install
npx skills add https://github.com/Z43L/zeus-agent --skill 1password-z43l
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1password
Source: https://github.com/Z43L/zeus-agent/tree/main/optional-skills/security/1password
Command: npx skills add https://github.com/Z43L/zeus-agent --skill 1password-z43l

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents leaking sensitive credentials by helping you store, retrieve, and inject secrets from 1Password instead of copying them into plaintext environment variables or files.

Core Features & Use Cases

  • Service-account based secret access: Uses OP_SERVICE_ACCOUNT_TOKEN for non-interactive automation of op read, op inject, and op run.
  • Interactive desktop app integration: Supports op signin with approval prompts and stable authenticated sessions for terminal workflows.
  • Connect server support: Enables self-hosted Connect endpoints using OP_CONNECT_HOST and OP_CONNECT_TOKEN.
  • Template and command workflows: Injects secrets into configs via op inject and runs commands with secret-bearing environment variables using op run.

Quick Start

Configure the service account token by setting OP_SERVICE_ACCOUNT_TOKEN in ~/.hermes/.env, then verify access with op whoami.

Frequently Asked Questions about 1password

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I inject secrets into configuration files using 1Password CLI?

You can inject secrets into configuration files using the `op inject` command. This replaces plaintext credential variables in your templates with actual secret references, preventing sensitive values from being exposed in your local environment.

How do I use 1Password CLI for CI/CD automation without interactive prompts?

Use a service account token for non-interactive secret access in CI/CD automation. Set the `OP_SERVICE_ACCOUNT_TOKEN` environment variable to authenticate `op read`, `op inject`, and `op run` commands automatically without requiring manual sign-in prompts.

Can I run commands with secret environment variables using 1Password CLI?

Yes, you can run commands with secret-bearing environment variables using `op run`. It retrieves the specified credentials securely and passes them to your application process, ensuring raw secrets are never printed directly to the terminal.

Does 1Password CLI support self-hosted Connect servers for secret management?

Yes, 1Password CLI supports self-hosted Connect endpoints. Configure the `OP_CONNECT_HOST` and `OP_CONNECT_TOKEN` environment variables to authenticate and retrieve secrets directly from your own Connect server infrastructure.

What are the limitations when handling secrets with 1Password CLI?

A key limitation is the strict requirement to avoid printing raw secrets to logs. You must adhere to operational guardrails when using `op read` or `op inject` to ensure sensitive credentials are never accidentally exposed in terminal output or CI logs.