Skip to main content
Alison Aquinas logoAlison's LLM Skills Marketplace

1password-cli

Included in skill bundleci-cdView on GitHub ↗

Files

SKILL.mdagentsreferences

Install

Install only this skill with npx skills
npx skills add alisonaquinas/llm-ci-dev --skill '1password-cli' -g -y
Install the containing skill bundle
/plugin install ci-cd@llm-skills
Download 1password-cli-skill.zip
This skill is bundled inside ci-cd. Use npx skills when you only want this skill, or install the bundle once to make every included skill available through the plugin marketplace flow. Browse the full skill bundle repository at github.com/alisonaquinas/llm-ci-dev.

Invoke

Invoke this skill after installation
/ci-cd:1password-cli

SKILL.md


name: 1password-cli description: Access 1Password secrets and run commands via op CLI. Use when tasks mention 1password-cli, op, 1Password, secret references (op://), op run, or service account tokens.

1Password CLI

Intent Router

RequestReferenceLoad When
Install, first-time setup, env varsreferences/install-and-setup.mdUser needs to install op or configure service account tokens
CLI commands, item operationsreferences/command-cookbook.mdUser needs signin/item get/list/create/edit/delete/read/run commands
Secret references, op run, injectreferences/secret-references-and-op-run.mdUser asks about op:// syntax, op run, op inject, or .env file injection
Service accounts, Connect serverreferences/service-accounts-and-connect.mdUser asks about OP_SERVICE_ACCOUNT_TOKEN, Connect server, or machine auth

Quick Start

# 1. Install (macOS)
brew install 1password-cli

# 2. Sign in
op signin

# 3. List vaults
op vault list

# 4. Retrieve a secret field
op item get "My App" --vault "Private" --fields password

# 5. Inject secrets into a command via secret references
op run -- env

Core Command Tracks

  • Sign in: op signin, op account list
  • Read a field: op read "op://vault/item/field"
  • Get item: op item get <name> --vault <vault> --format json
  • List items: op item list --vault <vault>
  • Create/edit/delete: op item create, op item edit, op item delete
  • Inject and run: op run -- <command>, op inject -i template.env
  • Documents: op document get <name>

Safety Guardrails

  • Never commit OP_SERVICE_ACCOUNT_TOKEN or session tokens to version control; use encrypted CI/CD secret storage.
  • Scope service accounts to the minimum set of vaults required.
  • Prefer op run or op inject over extracting secrets into shell variables that may appear in logs.
  • Rotate service account tokens regularly and revoke tokens for decommissioned pipelines.
  • Use secret references (op://vault/item/field) in config files instead of hardcoded values.
  • Avoid logging the output of op read or op item get in CI pipelines.

Workflow

  1. Install op and authenticate with op signin or set OP_SERVICE_ACCOUNT_TOKEN.
  2. Verify access with op vault list and op item list.
  3. Use op read "op://vault/item/field" to retrieve individual field values.
  4. Use op run -- <command> to inject secrets as environment variables for a single command.
  5. Use op inject -i .env.tpl -o .env for file-based secret injection.
  6. In CI/CD, set OP_SERVICE_ACCOUNT_TOKEN as an encrypted secret and use op run in pipeline steps.
# CI service account example: inject secrets without interactive sign-in
export OP_SERVICE_ACCOUNT_TOKEN="ops_eyJzaWduSW5BZGRyZXNzIjoiaHR0cHM..."
op run -- printenv | grep MY_API_KEY

Related Skills

  • aws — AWS CLI; combine with 1Password to retrieve AWS credentials at runtime
  • ci-architecture — patterns for secret injection using op run in GitHub Actions or GitLab CI
  • direnv — using .envrc with op run for local development secret loading
  • aws-secretsmanager — AWS-native alternative for secrets stored in AWS environments

References

← Back to marketplace