1password

Retrieve and inject 1Password secrets via op CLI for command execution.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/devMoez/titan --skill 1password-devmoez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1password
Source: https://github.com/devMoez/titan/tree/main/optional-skills/security/1password
Command: npx skills add https://github.com/devMoez/titan --skill 1password-devmoez

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you avoid leaking secrets by replacing plaintext environment variables or checked-in secret files with secure retrieval and injection from 1Password using the op CLI.

Core Features & Use Cases

  • Secure secret retrieval: Reads secrets from 1Password vault items and fields using op read.
  • Safe secret injection for configs/templates: Injects secret values into templates at runtime via op inject without permanently storing them.
  • Execution with secret env vars: Runs commands using secret-backed environment variables through op run.
  • Use Cases: Provisioning dev/ops environments, pulling DB credentials/OTPs, and generating runtime configuration files safely for CI, local dev, or server automation.

Quick Start

Authenticate for automation by setting OP_SERVICE_ACCOUNT_TOKEN in ~/.Titan/.env, then run an op read command for the secret you need.

Frequently Asked Questions about 1password

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

FAQPage Schema
How do I inject secrets into configuration templates at runtime using 1Password?

You can inject secrets into configuration templates at runtime using the op inject command. This retrieves values from your 1Password vault and populates templates without permanently storing plaintext credentials on disk.

How do I run commands with secret environment variables from 1Password in CI?

To run commands with secret environment variables in CI, use op run. It dynamically loads credentials from 1Password into your command's environment, supporting non-interactive service account flows for automation.

Do I need a service account token to retrieve secrets in server automation?

Yes, server automation requires a service account token. You must set OP_SERVICE_ACCOUNT_TOKEN in your environment to enable non-interactive secret retrieval and injection via the op CLI.

What is the best way to avoid leaking plaintext credentials in DevOps environments?

The best way to avoid leaking plaintext credentials in DevOps is replacing checked-in files with secure 1Password retrieval. Using op read, inject, and run ensures secrets are pulled dynamically at runtime rather than stored statically.

Can I use the 1Password CLI for both local terminal and server automation scenarios?

Yes, the 1Password CLI supports both local terminal and server automation scenarios. It handles interactive desktop app integration for local dev and non-interactive service account flows for CI and servers.

What are the limitations of using 1Password service accounts for secret management?

A limitation of using 1Password service accounts is the strict op CLI version requirement. You must install op CLI v2.18.0 or higher, and have a valid 1Password account to authenticate non-interactive automation flows.