1password

Retrieve and inject secrets from 1Password CLI into command workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents leaking credentials by helping you use 1Password CLI to store, read, and inject secrets at execution time instead of hardcoding plaintext tokens or committing secret files.

Core Features & Use Cases

  • Service account secret management: Read and inject secrets non-interactively using OP_SERVICE_ACCOUNT_TOKEN.
  • Desktop app integration (interactive): Use op signin with CLI integration for accounts that prefer approval via the desktop app.
  • Connect server support: Enable self-hosted Connect authentication using OP_CONNECT_HOST and OP_CONNECT_TOKEN.
  • Template injection and secret execution: Use op inject and op run to render configs and run commands with secret-backed environment variables.

Quick Start

Ask Hermes to set up the 1Password CLI using your 1Password Service Account Token and then read a secret reference like op://Vault/Item/field and inject it into your command or template.

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 command execution workflows using 1Password CLI?

You can inject secrets into command execution workflows using 1Password CLI by utilizing `op inject` to render config templates and `op run` to execute commands with secret-backed environment variables.

Can I automate secret retrieval non-interactively for CI pipelines with 1Password?

Yes, you can automate non-interactive secret retrieval for CI pipelines by setting the `OP_SERVICE_ACCOUNT_TOKEN` environment variable, which allows the 1Password CLI to read and inject secrets headlessly.

Does 1Password CLI support self-hosted Connect server environments?

Yes, 1Password CLI supports self-hosted Connect server environments by using the `OP_CONNECT_HOST` and `OP_CONNECT_TOKEN` configuration variables for authentication in CI or headless setups.

What is the best way to manage secrets safely without hardcoding plaintext tokens?

The best way to manage secrets safely without hardcoding plaintext tokens is to use 1Password CLI to store, read, and inject credentials securely at execution time via service accounts or desktop app integration.

Do I need to use interactive signin to read secret references with 1Password CLI?

No, you do not need interactive signin to read secret references; you can use a service account token for automation or use interactive `op signin` for desktop app integration depending on your environment.

Why should I use template injection instead of exporting secret files directly?

You should use template injection with `op inject` instead of exporting secret files directly to prevent leaking credentials and avoid committing plaintext tokens, ensuring secrets are only resolved at runtime.