From atum-stack-backend
Set up and use the 1Password CLI (op) to securely read, inject, and run secrets within development workflows. Use when you need to access credentials, API keys, or any sensitive values stored in 1Password vaults.
npx claudepluginhub arnwaldn/atum-plugins-collection --plugin atum-stack-backendThis skill uses the workspace's default tool permissions.
CRITICAL: Never paste secrets into logs, chat, or code files. Always use `op run` or `op inject` to inject secrets at runtime.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides implementation of event-driven hooks in Claude Code plugins using prompt-based validation and bash commands for PreToolUse, Stop, and session events.
CRITICAL: Never paste secrets into logs, chat, or code files. Always use op run or op inject to inject secrets at runtime.
op --versionop --versionop signin (the desktop app will prompt for authorization)op whoami--account <account-shorthand> or set OP_ACCOUNT.# Format: op://vault-name/item-name/field-name
op read "op://Private/GitHub/token"
# Preferred: never write secrets to disk
op run --env-file=".env.op-template" -- npm run dev
DATABASE_URL=op://Dev/Postgres/connection-string
API_KEY=op://Private/MyService/credential
op inject -i config.template.yaml -o config.yaml
op vault list
op item list --vault="Private"
op item get "GitHub" --vault="Private" --fields="username,token"
op run / op inject over reading secrets with op read into a shell variable.op signin again and authorize in the desktop app.op is not available, stop and ask the user to install the 1Password CLI before proceeding.