one-password

Manage 1Password secrets in a persistent tmux session.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/Khang5687/agent-scripts --skill one-password
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: one-password
Source: https://github.com/Khang5687/agent-scripts/tree/main/skills/one-password
Command: npx skills add https://github.com/Khang5687/agent-scripts --skill one-password

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires 1password-cli, tmux, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of managing and accessing 1Password secrets, reducing the need for multiple interactions and ensuring secure operations within a single tmux session.

Core Features & Use Cases

  • Persistent Tmux Session: Manages all secret operations within a single, persistent tmux session.
  • Service Account Access: Supports non-interactive service-account tokens for secure vault access.
  • Desktop App Fallback: Provides a secure fallback for accessing the 1Password desktop app if needed.
  • Item Creation/Editing: Facilitates the creation and editing of items in the 1Password vault without exposing secrets.
  • Use Case: Automate secret management tasks like signing in, retrieving items, and storing new secrets with a single, secure command.

Quick Start

Use the one-password skill to retrieve your 'Service API Tokens' from the 1Password vault.

Frequently Asked Questions about one-password

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

FAQPage Schema
How do I manage 1Password secrets from the command line without repeated sign-ins?

You can manage 1Password secrets from the command line by automating sign-in, token retrieval, and item editing within a single persistent tmux session. This approach handles authentication once and maintains secure vault access across multiple operations.

Can I use a service account token for non-interactive 1Password vault access?

Yes, 1Password vault access supports non-interactive service account tokens. This allows automated secret retrieval and management without requiring manual authentication prompts during your terminal workflow.

Do I need the 1Password CLI and tmux installed to automate secret retrieval?

Yes, both the 1Password CLI and tmux are required dependencies. The 1Password CLI handles vault authentication and item operations, while tmux provides the persistent session environment needed to maintain secure state.

What's the best way to create and edit items in a 1Password vault programmatically?

The best way to create and edit 1Password vault items programmatically is by running scripted operations within a dedicated tmux session. This method facilitates item creation and editing without exposing secrets directly in your terminal history.

Does 1Password CLI work with the desktop app as a fallback for authentication?

Yes, 1Password CLI integration provides a secure fallback to the 1Password desktop app when needed. This ensures vault access remains available even if service account tokens are not configured or encounter issues.

Why does my 1Password session expire when retrieving secrets across multiple terminal windows?

1Password sessions typically expire across multiple windows because authentication state is not shared. Running secret management operations within a single persistent tmux session resolves this by maintaining a continuous authenticated state.