1password

Retrieve and inject 1Password CLI secrets without exposing credentials.

1|1|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/Kjdragan/universal_agent --skill 1password-kjdragan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1password
Source: https://github.com/Kjdragan/universal_agent/tree/main/.claude/skills/1password
Command: npx skills add https://github.com/Kjdragan/universal_agent --skill 1password-kjdragan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables teams to securely manage and retrieve secrets by installing and configuring the 1Password CLI (op), authenticating, and reading or injecting sensitive data without exposing credentials in logs or code.

Core Features & Use Cases

  • Secret retrieval: Sign in to 1Password and read secrets from op vaults without leaking credentials.
  • Secret injection: Inject secrets into environments or configurations for automated workflows.
  • Multi-account support: Seamlessly switch between accounts and vaults during development and deployment.

Quick Start

Install and configure the 1Password CLI following the official get-started steps, then sign in using op signin inside a dedicated tmux session. Use op whoami to verify authentication and op read op://<vault>/<item> to fetch a secret, or op inject to inject secrets into a target file or environment.

Frequently Asked Questions about 1password

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

FAQPage Schema
How do I retrieve secrets from a 1Password vault in an automated deployment pipeline?

You can retrieve secrets from a 1Password vault by signing in via the op CLI inside a dedicated tmux session and using `op read` to fetch values without exposing credentials in logs or code.

What is the best way to inject 1Password secrets into a configuration file?

The best way to inject 1Password secrets into a configuration file is by using the `op inject` command, which securely populates target files or environments with sensitive data fetched directly from your vaults.

Does the 1Password CLI require a separate authentication session for automated secret access?

Yes, the 1Password CLI requires a dedicated tmux session for authentication and secret access, assuming the op binary is installed and desktop integration is configured to securely manage vault data.

Can I switch between multiple 1Password accounts during interactive development sessions?

Yes, you can seamlessly switch between multiple accounts and vaults during development and deployment sessions to retrieve and inject secrets across different environments as needed.

Why use a dedicated tmux session for 1Password CLI sign-in?

Using a dedicated tmux session for 1Password CLI sign-in ensures that authentication and secret access processes remain isolated and persistent, preventing credentials from being exposed in logs or interactive code.