Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 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

    3 usesSecurity 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.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.

    Requires 1Password desktop app for integration. Requires tmux to be installed on the host system for session isolation.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    3 uses

    Times used to date

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 2 months ago

    • Free with an Agensi account

    Permissions

    Terminal / Shell
    Listed2 months ago

    What's inside

    Frequently Asked Questions

    This skill provides a secure interface for the 1Password CLI (op), allowing you to search, create, and inject secrets into your workflows without them ever appearing in your shell history or disk-based configuration files.

    You will need the 1Password desktop app installed with CLI integration enabled; the skill handles the remaining setup, including tmux-isolated authentication flows to keep your sessions secure.

    Yes, the skill is designed to handle multiple accounts and vaults, allowing you to seamlessly switch between personal, team, or client environments using standard 1Password CLI patterns.

    This skill is optimized for AI agents that support terminal execution and tool calling, such as those running in VS Code, Cursor, or local developer environments.

    While optimized for desktop integration, the skill can function in headless environments if you have a 1Password Service Account token configured in your system environment.

    You receive the full skill definition, including the specialized logic for tmux-socket isolation and secure secret injection, along with documentation for immediate deployment.

    New in Security

    Free