Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseOpenClawOpenClaw+21 more

    1Password CLI Vault Operations

    1

    Manage secrets with 1Password CLI (op): tmux-isolated sign-in, vault item ops, and safe injection or execution without exposing secrets.

    Free

    2 installsSecurity scanned
    1Password CLI Vault Operations

    1Password CLI Vault Operations

    Example session with this skill installed

    I'm setting up our deployment agent to pull production secrets from 1Password. The desktop app is installed on this Linux box but CLI integration isn't hooked up yet, and we have two accounts — personal at my.1password.com and the team vault at team.1password.com. Walk me through installing op, enabling desktop integration, and signing into the team account so I can run node server.js with vault environment variables without writing any secret to disk. Then show me how to verify with whoami, list items in the Development vault, and tear down the session afterwards.

    • Read your context and instructions
    • Compiled the 1password cli vault

    Summary

    1Password CLI is installed, desktop integration is enabled, and the team account is signed in through an isolated tmux session. node server.js now receives vault secrets at runtime via op run, with nothing persisted to disk or printed to logs.

    Vault Access Runbook

    StepCommandVerified State
    Installbrew install 1password-cli (Linux: official package)op --version returns 2.30.x
    Connect appSettings -> Developer -> enable 'Connect with 1Password CLI'Desktop app unlocked
    Sign in (tmux)tmux -S $SOCKET new -d -s op-auth-<ts> then op signin --account team.1password.comop whoami prints team account
    List itemsop item list --vault 'Development'14 items visible
    Inject at runtimeop run --env-file .env.template -- node server.jsApp boots; no secrets in ps or logs
    Cleanuptmux -S $SOCKET kill-session -t $SESSIONSocket dir empty, session gone

    Never redirect op item get output into a file — use op inject / op run exclusively.

    Next steps

    • Approve the desktop prompt that appeared during signin, then re-run op whoami to confirm
    • Export OP_ACCOUNT=team.1password.com inside the session to skip --account on every call
    • If tmux is missing, install it first — do not run op outside an isolated session
    • For headless CI, switch to op account add with a service-account token

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem

    Managing secrets manually leads to plain-text leaks in shell history, logs, or .env files. Developers often struggle with re-authenticating CLI tools in non-interactive environments or complex multi-account setups.

    What it does

    • Automates secure 1Password CLI (op) installation and desktop integration checks.
    • Executes authentication flows inside isolated tmux sessions to prevent session hijacking and credential leakage.
    • Performs vault operations like item creation, searching, and retrieval without writing data to disk.
    • Injects secrets directly into runtime environments using op run and op inject patterns.

    Frameworks & tools

    1Password CLI (op), tmux, Bash/Zsh, and 1Password Desktop Integration.

    Why this beats prompting it yourself

    General prompts often ignore the security risks of shell history or interactive auth prompts that hang in background processes. This skill enforces a hardened tmux-socket isolation pattern and strictly uses non-persistent injection methods to ensure secrets never touch your persistent storage.

    Use cases

    • Provisioning temporary environment variables for local development servers.
    • Automating the creation of secure credentials for new microservices.
    • Managing multiple 1Password accounts across different client or team vaults.
    • Auditing vault contents via CLI without exposing sensitive values to the console.

    Known limitations

    Requires the 1Password desktop app for the standard auth flow. Headless or CI environments require manual service account token configuration.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    2 installs

    Downloaded by developers to date

    Free forever

    No account required to browse

    Trust & safety

    Security scanned

    Verified clean 11 days ago

    • Free to download with an account

    Listed11 days ago

    What's inside

    Frequently Asked Questions