1password

Manage secrets securely with the 1Password CLI in Hermes workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps securely manage and access secrets by using the 1Password CLI, eliminating the need to store sensitive data in plaintext environment variables or configuration files.

Core Features & Use Cases

  • Sign in and authenticate with 1Password CLI to access secrets at runtime.
  • Read, inject, and use secrets in automation and scripts without exposing them in code.
  • Support multiple authentication methods (desktop app integration, service account tokens) and run commands with secrets in Hermes workflows.

Quick Start

Install the 1Password CLI, sign in, and verify your session so Hermes can read and inject secrets securely.

Frequently Asked Questions about 1password

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

FAQPage Schema
How do I manage secrets securely without storing credentials in environment variables?

Use the 1Password CLI to retrieve and inject credentials at runtime, avoiding plaintext environment variables or configuration files. This skill supports desktop integration and service account tokens for secure secret management.

How do I inject secrets into automation scripts using the 1Password CLI?

Inject secrets into automation scripts by authenticating with the 1Password CLI and retrieving credentials at runtime within tmux-enabled Hermes sessions, ensuring sensitive data is never exposed in your code.

Do I need a tmux-enabled session to automate 1Password CLI sign-in?

Yes, a tmux-enabled Hermes session is required for non-interactive automation. You also need the op CLI installed and an authentication method chosen, such as desktop app integration or service account tokens.

What authentication methods does the 1Password CLI support for retrieving secrets?

The 1Password CLI supports multiple authentication methods for retrieving secrets, including desktop app integration and service account tokens, allowing flexible secure access across different automation workflows.

Why should I use the 1Password CLI instead of plaintext config files for secrets?

Use the 1Password CLI to avoid embedding credentials in plaintext config files, preventing sensitive data exposure. It securely reads and injects secrets at runtime, keeping credentials out of your codebase.

Can I use service account tokens to authenticate with the 1Password CLI in automated workflows?

Yes, service account tokens are supported as an authentication method for the 1Password CLI, enabling automated secret retrieval and runtime injection in Hermes workflows without interactive sign-in.