Smithery Logo
MCPsSkillsDocsPricing
Login
Smithery Logo

Accelerating the Agent Economy

Resources

DocumentationPrivacy PolicySystem Status

Company

PricingAboutBlog

Connect

© 2026 Smithery. All rights reserved.

    balaraj74

    1password

    balaraj74/1password
    Security
    1 installs

    About

    SKILL.md

    Install

    Install via Skills CLI

    or add to your agent
    • Claude Code
      Claude Code
    • Codex
      Codex
    • OpenClaw
      OpenClaw
    • Cursor
      Cursor
    • Amp
      Amp
    • GitHub Copilot
      GitHub Copilot
    • Gemini CLI
      Gemini CLI
    • Kilo Code
      Kilo Code
    • Junie
      Junie
    • Replit
      Replit
    • Windsurf
      Windsurf
    • Cline
      Cline
    • Continue
      Continue
    • OpenCode
      OpenCode
    • OpenHands
      OpenHands
    • Roo Code
      Roo Code
    • Augment
      Augment
    • Goose
      Goose
    • Trae
      Trae
    • Zencoder
      Zencoder
    • Antigravity
      Antigravity
    ├─
    ├─
    └─

    About

    Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.

    SKILL.md

    1Password CLI

    Follow the official CLI get-started steps. Don't guess install commands.

    References

    • references/get-started.md (install + app integration + sign-in flow)
    • references/cli-examples.md (real op examples)

    Workflow

    1. Check OS + shell.
    2. Verify CLI present: op --version.
    3. Confirm desktop app integration is enabled (per get-started) and the app is unlocked.
    4. REQUIRED: create a fresh tmux session for all op commands (no direct op calls outside tmux).
    5. Sign in / authorize inside tmux: op signin (expect app prompt).
    6. Verify access inside tmux: op whoami (must succeed before any secret read).
    7. If multiple accounts: use --account or OP_ACCOUNT.

    REQUIRED tmux session (T-Max)

    The shell tool uses a fresh TTY per command. To avoid re-prompts and failures, always run op inside a dedicated tmux session with a fresh socket/session name.

    Example (see tmux skill for socket conventions, do not reuse old session names):

    SOCKET_DIR="${FRIDAY_TMUX_SOCKET_DIR:-${TMPDIR:-/tmp}/friday-tmux-sockets}"
    mkdir -p "$SOCKET_DIR"
    SOCKET="$SOCKET_DIR/friday-op.sock"
    SESSION="op-auth-$(date +%Y%m%d-%H%M%S)"
    
    tmux -S "$SOCKET" new -d -s "$SESSION" -n shell
    tmux -S "$SOCKET" send-keys -t "$SESSION":0.0 -- "op signin --account my.1password.com" Enter
    tmux -S "$SOCKET" send-keys -t "$SESSION":0.0 -- "op whoami" Enter
    tmux -S "$SOCKET" send-keys -t "$SESSION":0.0 -- "op vault list" Enter
    tmux -S "$SOCKET" capture-pane -p -J -t "$SESSION":0.0 -S -200
    tmux -S "$SOCKET" kill-session -t "$SESSION"
    

    Guardrails

    • Never paste secrets into logs, chat, or code.
    • Prefer op run / op inject over writing secrets to disk.
    • If sign-in without app integration is needed, use op account add.
    • If a command returns "account is not signed in", re-run op signin inside tmux and authorize in the app.
    • Do not run op outside tmux; stop and ask if tmux is unavailable.
    Recommended Servers
    Cloudflare
    Cloudflare
    Discord
    Discord
    AurelianFlo
    AurelianFlo
    Repository
    balaraj74/f.r.i.d.a.y
    Files