1password

Manage and inject 1Password secrets into applications and CLI workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the friction of handling secrets in development and automation by enabling secure retrieval and injection of credentials into commands and runtime environments without persisting plaintext secrets.

Core Features & Use Cases

  • Sign-in and authentication workflows: guidance for desktop app integration, service account token setup, and Connect server configuration to authenticate the 1Password CLI.
  • Secret retrieval and runtime injection: read secrets, get OTPs, inject templates, and run commands with secret environment variables using op read, op inject, and op run.
  • Operational patterns for reliability: advice for running sign-in and secret operations in a persistent tmux session for interactive desktop flows and notes for headless/CI usage with OP_SERVICE_ACCOUNT_TOKEN.

Quick Start

Sign in or configure a service account, read the secret op://app-prod/db/password, and run the deployment command with that secret injected.

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 environment variables for CLI workflows?

To inject secrets into environment variables, use the 1Password CLI `op run` command to execute your application with secret references automatically resolved. This approach prevents persisting plaintext credentials in your local development or CI automation environments.

What is the best way to manage 1Password secrets in headless CI pipelines?

The best way to manage 1Password secrets in headless CI pipelines is by setting the `OP_SERVICE_ACCOUNT_TOKEN` environment variable to authenticate the 1Password CLI. This enables automated secret retrieval and injection without requiring interactive desktop sign-in.

Can I use 1Password CLI to read secrets and OTPs during local development?

Yes, you can use the `op read` command in the 1Password CLI to retrieve secrets and one-time passwords during local development. Interactive desktop sessions authenticate via desktop app integration to securely access your vault items.

How do I populate configuration files with secrets using 1Password?

You can populate configuration files with secrets using the `op inject` command. It processes a template file containing secret references and outputs a rendered configuration file with the actual secret values securely injected into the matching placeholders.

Do I need tmux to run 1Password CLI in interactive desktop sessions?

Using tmux is recommended for running 1Password CLI operations in interactive desktop flows. A persistent tmux session helps maintain stable desktop app integration and authentication state for reliable secret retrieval and runtime injection.