1password

Étoiles4

Forks0

Mis à jour27 avril 2026 à 19:57

Set up and use 1Password CLI for sign-in, desktop integration, and reading or injecting secrets.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

Agent-Pattern-Labs

Agent-Pattern-Labs/sparse-kernel

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Administrateurs de réseaux et de systèmes informatiquesProfessions informatiques et mathématiques·SOC 15-1244

Explorateur de fichiers

3 fichiers

SKILL.md

readonly

name	1password
description	Set up and use 1Password CLI for sign-in, desktop integration, and reading or injecting secrets.
homepage	https://developer.1password.com/docs/cli/get-started/
metadata	{"openclaw":{"emoji":"🔐","requires":{"bins":["op"]},"install":[{"id":"brew","kind":"brew","formula":"1password-cli","bins":["op"],"label":"Install 1Password CLI (brew)"}]}}

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

Check OS + shell.
Verify CLI present: op --version.
Confirm desktop app integration is enabled (per get-started) and the app is unlocked.
REQUIRED: create a fresh tmux session for all op commands (no direct op calls outside tmux).
Sign in / authorize inside tmux: op signin (expect app prompt).
Verify access inside tmux: op whoami (must succeed before any secret read).
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="${OPENCLAW_TMUX_SOCKET_DIR:-${TMPDIR:-/tmp}/openclaw-tmux-sockets}"
mkdir -p "$SOCKET_DIR"
SOCKET="$SOCKET_DIR/openclaw-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.

Plus depuis ce dépôt

même dépôt

blacksmith-testbox

Agent-Pattern-Labs/sparse-kernel

Run Blacksmith Testbox for CI-parity checks, secrets, hosted services, migrations, or builds local cannot reproduce.

2026-04-274

openclaw-ghsa-maintainer

Agent-Pattern-Labs/sparse-kernel

Inspect, patch, validate, publish, or confirm OpenClaw GHSA security advisories and private-fork state.

2026-04-274

openclaw-parallels-smoke

Agent-Pattern-Labs/sparse-kernel

Run, rerun, debug, or interpret OpenClaw Parallels install, onboarding, gateway smoke, and upgrade checks.

2026-04-274

openclaw-pr-maintainer

Agent-Pattern-Labs/sparse-kernel

Review, triage, close, label, comment on, or land OpenClaw PRs/issues with maintainer evidence checks.

2026-04-274

openclaw-qa-testing

Agent-Pattern-Labs/sparse-kernel

Run, watch, debug, extend, or explain OpenClaw qa-lab and qa-channel scenarios, artifacts, and live lanes.

2026-04-274

openclaw-release-maintainer

Agent-Pattern-Labs/sparse-kernel

Prepare or verify OpenClaw stable/beta releases, changelogs, release notes, publish commands, and artifacts.

2026-04-274

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

Check OS + shell.

Verify CLI present: op --version.

Confirm desktop app integration is enabled (per get-started) and the app is unlocked.

REQUIRED: create a fresh tmux session for all op commands (no direct op calls outside tmux).

Verify access inside tmux: op whoami (must succeed before any secret read).

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="${OPENCLAW_TMUX_SOCKET_DIR:-${TMPDIR:-/tmp}/openclaw-tmux-sockets}" mkdir -p "$SOCKET_DIR" SOCKET="$SOCKET_DIR/openclaw-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.