1password

Integrate 1Password CLI into Cronus workflows for secret retrieval and injection.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

1Password CLI enables secure management of secrets within Cronus workflows, replacing plaintext env vars and exposed credentials.

Core Features & Use Cases

  • Sign-in, read, and inject secrets using op into templates or runtime commands.
  • Supports Desktop App integration and Service Account token flows for non-interactive environments.
  • Use case: securely populate configuration files and environment variables during Cronus sessions.

Quick Start

Sign in to the 1Password CLI and configure your authentication method for Cronus usage.

Frequently Asked Questions about 1password

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

FAQPage Schema
How do I manage secrets securely in Cronus workflows without exposing plaintext environment variables?

Secure secret management in Cronus is achieved by integrating the 1Password CLI. It replaces plaintext environment variables and exposed credentials by retrieving secrets at runtime and injecting them directly into templates or commands.

How do I authenticate the 1Password CLI for non-interactive Cronus terminal sessions?

To authenticate the 1Password CLI for non-interactive environments, configure a Service Account token. Alternatively, you can use the Desktop App integration with desktop connect for interactive sessions within the Cronus terminal.

Does the 1Password CLI integration require any specific authentication setup before retrieving secrets?

Yes, 1Password CLI integration requires the op CLI installed and an appropriate authentication method configured. You must set up either a Service Account token or desktop app connect before retrieving and injecting secrets.

What is the best way to inject secrets into configuration files during a Cronus session?

The best way to inject secrets into configuration files is using the 1Password CLI within Cronus. It securely populates templates and runtime environment variables by fetching credentials via the op command during active sessions.

Are there limitations when using service accounts versus the desktop app for 1Password CLI authentication?

Service account tokens are designed for non-interactive environments, while the desktop app connect flow supports interactive usage. Both methods require adherence to guardrails for injecting secrets safely into Cronus commands.

Why use 1Password CLI over plaintext environment variables for secret management in Cronus?

Using 1Password CLI provides secure secret management by replacing exposed credentials. It integrates directly into Cronus workflows to fetch secrets dynamically via the op CLI, preventing sensitive data from lingering in plaintext environment variables.