1password

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Secrets management is error-prone when credentials are stored in plaintext or scattered across configuration files. This Skill provides a structured way to interact with the 1Password CLI to securely access, read, and inject secrets into applications and scripts, reducing exposure and manual handling.

Core Features & Use Cases

  • Read secrets from vaults using op read and inject them into templates with op inject.
  • Sign in and authenticate via desktop app, service accounts, or Connect server to support both interactive and headless environments.
  • Execute commands with secrets in a secure, isolated Hermes workflow using op run inside a tmux session to maintain auth context.

Quick Start

Install and configure the 1Password CLI, sign in, then use op read, op inject, and op run to securely access and apply secrets.

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 using the 1Password CLI in automated workflows?

You can manage secrets securely using the 1Password CLI by integrating commands like op read and op inject into automated workflows to access and apply credentials without storing them in plaintext configuration files.

How do I use op run to inject secrets into scripts inside a tmux session?

You use op run within a tmux session to execute commands with injected secrets, maintaining the authentication context non-interactively to ensure secure, isolated runtime secret usage in headless environments.

Can I authenticate the 1Password CLI using a service account for headless environments?

Yes, you can authenticate the 1Password CLI using service accounts or a Connect server to support both interactive desktop app integration and headless automated environments for secure secret access.

What is the best way to prevent plaintext secret exposure in configuration files?

The best way to prevent plaintext secret exposure is to use op inject to populate configuration templates directly from 1Password vaults, eliminating the need to scatter credentials across local files.

Does this approach require the 1Password desktop app to be running for tmux automation?

No, while desktop app integration is supported for interactive use, you can authenticate via service accounts or a Connect server to run automated tmux workflows without the desktop app.

When should I not use op inject for secret management?

You should avoid using op inject if you lack 1Password CLI installation or proper authentication methods, as these are required prerequisites for securely reading and injecting vault secrets.