Agent skill · security · nousresearch
1password
Set up op CLI, sign in, and read or inject secrets.
Why this skill is useful
Adds specific commands and workflows for managing secrets with 1Password CLI that the AI wouldn't reliably generate on its own.
What it needs
Requires 1password-cli, tmux installed locally. Requires 1password account access. About 2k tokens when loaded. Last updated 2026-08-07. 226,679 stars on the source repository.
What this skill does
1Password CLI Use this skill when the user wants secrets managed through 1Password instead of plaintext env vars or files. Requirements 1Password account 1Password CLI (op) installed One of: desktop app integration, service account token (OPSERVICEACCOUNTTOKEN), or Connect server tmux available for stable authenticated sessions during Hermes terminal calls (desktop app flow only) When to Use Install or configure 1Password CLI Sign in with op signin Read secret references like op://Vault/Item/field Inject secrets into config/templates using op inject Run commands with secret env vars via op run Authentication Methods Service Account (recommended for Hermes) Set OPSERVICEACCOUNTTOKEN in ${HERMESHOME:-~/.hermes}/.env (the skill will prompt for this on first load). No desktop app needed. Supports op read, op inject, op run. Desktop App Integration (interactive) 1. Enable in 1Password desktop app: Settings → Developer → Integrate with 1Password CLI 2. Ensure app is unlocked 3. Run op signin and approve the biometric prompt Connect Server (self-hosted) Setup 1. Install CLI: 2. Verify: 3. Choose an auth method above and configure it. Hermes Execution Pattern (desktop app flow) Hermes terminal commands are non-interactive by default and can lose auth context between calls. For reliable op use with desktop app integration, run sign-in and secret operations inside a dedicated tmux session. Note: This is NOT needed when using OPSERVICEACCOUNTTOKEN — the token persists across terminal calls automatically. Common Operations Read a secret Get OTP Inject into template Run a command with secret env var Guardrails Never print raw secrets back to user unless they explicitly request the value. Prefer op run / op inject instead of writing secrets into files. If command fails with "account is not signed in", run op signin again in the same tmux session. If desktop app integration is unavailable (headless/CI), use service account token flow. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nousresearch/1password