1password

Configure 1Password CLI authentication and inject secret references into terminal commands.

3|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/twjarviszyra-web/hermes-unbound --skill 1password-twjarviszyra-web
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1password
Source: https://github.com/twjarviszyra-web/hermes-unbound/tree/main/optional-skills/security/1password
Command: npx skills add https://github.com/twjarviszyra-web/hermes-unbound --skill 1password-twjarviszyra-web

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the friction and risk of handling secrets manually by helping you use 1Password as a secure source for command-line credentials, API keys, and one-time passwords.

Core Features & Use Cases

  • CLI Setup and Sign-In: Install and configure the op command-line tool for desktop app, service account, or Connect-based authentication.
  • Secret Reading and Injection: Retrieve secrets from 1Password references and inject them into templates or runtime environments without exposing plaintext values.
  • Automation-Friendly Workflows: Use protected secrets in scripts, local development, CI jobs, and other terminal-based workflows with safer handling patterns.
  • Use Case: A developer needs to run a deployment command that requires database credentials and an OTP, and this Skill guides them through authenticating, reading the secrets, and passing them securely to the command.

Quick Start

Ask the assistant to help you set up the 1Password CLI, authenticate with the right method, and use it to read or inject the secrets needed for your command.

Frequently Asked Questions about 1password

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

FAQPage Schema
How do I use the 1Password CLI to manage secrets in terminal workflows?

You can manage secrets in terminal workflows by using the 1Password CLI to authenticate, read secret references, and inject credentials into templates or runtime environments without exposing plaintext values.

What's the best way to inject secrets into scripts without exposing plaintext values?

Injecting secrets without exposing plaintext values is achieved by using the 1Password CLI to read secret references and pass them securely as protected environment variables to your runtime commands.

How do I authenticate the op CLI for headless automation contexts?

To authenticate the op CLI for headless automation contexts, you can configure it using a 1Password service account token or a Connect server instead of relying on desktop app integration.

Do I need a 1Password service account token to use op in CI jobs?

Yes, running op in CI jobs requires a 1Password account or service account token to enable headless authentication, as desktop app integration is typically unavailable in automated environments.

Can I use 1Password secret references to provide database credentials and OTPs for deployment commands?

Yes, you can use 1Password secret references to retrieve database credentials and one-time passwords, then pass them securely to deployment commands during interactive or headless terminal workflows.

What are the limitations of using 1Password CLI for secret management?

Limitations of 1Password CLI secret management include requiring a 1Password account or service account token, the op CLI installation, and support for desktop app integration, Connect server, or service-account authentication.