1password

Manage secrets with the 1Password CLI in Hermes workflows.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ar0cket1/Hermes-Agent-Online-RL --skill 1password-ar0cket1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1password
Source: https://github.com/ar0cket1/Hermes-Agent-Online-RL/tree/main/optional-skills/security/1password
Command: npx skills add https://github.com/ar0cket1/Hermes-Agent-Online-RL --skill 1password-ar0cket1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Centralize and secure secret management for Hermes workflows by leveraging the 1Password CLI, eliminating plaintext secrets in environment files and scripts.

Core Features & Use Cases

  • Manage secrets via the op CLI: sign in, read, inject, and run commands with secrets in a controlled way.
  • Supports desktop app integration and service accounts for automation, ensuring seamless non-interactive use in scripts.
  • Use cases include provisioning credentials, injecting passwords into templates, and securely validating access in Hermes executions.

Quick Start

Sign in to 1Password via the CLI, then read or inject secrets using op, within a tmux session for stable auth.

Frequently Asked Questions about 1password

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

FAQPage Schema
How do I inject secrets from the 1Password CLI into my scripts?

To inject secrets, use the 1Password CLI to read sensitive values and pass them directly into your templates or commands. This eliminates plaintext credentials by securely substituting values during execution.

Can I use 1Password CLI to automate secret access in CI environments?

Yes, 1Password CLI supports service accounts for non-interactive authentication, allowing you to securely automate secret access and provision credentials within CI environments.

What do I need to manage secrets with the op CLI in a terminal session?

You need the 1Password CLI installed, a valid authentication method like the desktop app or service account, and a tmux-based session to maintain stable auth context.

How does centralizing secrets with the 1Password CLI solve plaintext credential exposure?

Centralizing secrets with the 1Password CLI removes plaintext credentials from environment files and scripts by reading and injecting sensitive values on demand during execution.

Why does 1Password CLI require a tmux session for Hermes workflows?

A tmux-based Hermes session is required to maintain stable auth context, ensuring the 1Password CLI can securely access and inject secrets across local terminals without repeated authentication.

Does 1password work with desktop app integration for non-interactive script execution?

Yes, the skill supports desktop app integration and service accounts to ensure seamless non-interactive use when provisioning credentials or validating access in scripts.