1password

Retrieve secrets and automate sign-in via the 1Password CLI.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/NITISH-gitbit/hermes-custom --skill 1password-nitish-gitbit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1password
Source: https://github.com/NITISH-gitbit/hermes-custom/tree/main/optional-skills/security/1password
Command: npx skills add https://github.com/NITISH-gitbit/hermes-custom --skill 1password-nitish-gitbit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenges of password management and secrets handling, especially when dealing with the 1Password CLI, by centralizing and automating secret access, integration, and usage.

Core Features & Use Cases

  • Centralized Secret Access: Access secrets directly from 1Password CLI, avoiding the need for plaintext env vars or files.
  • Integration and Automation: Automate sign-in, secret retrieval, and injection, ideal for CI/CD pipelines and interactive terminal sessions.
  • Use Case: For instance, this Skill can automate the sign-in process and inject a 1Password service account token into an application, thereby simplifying and securing the deployment process.

Quick Start

Configure and run the 1Password CLI skill with a service account token: export OP_SERVICE_ACCOUNT_TOKEN="your-token-here"; op whoami to verify the service account.

Frequently Asked Questions about 1password

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate password management and retrieve secrets in a CI/CD pipeline?

Automate password management by integrating with the 1Password CLI to securely retrieve secrets, API keys, and passwords. This eliminates plaintext environment variables by injecting a 1Password service account token directly into your automated deployment workflows.

Can I use a 1Password service account token for automated secret access?

Yes, you can use a 1Password service account token for automated secret access. You configure the token by exporting it as an environment variable, then verify the authentication session to securely retrieve sensitive data without manual sign-in prompts.

What is the best way to avoid plaintext environment variables when handling passwords?

The best way to avoid plaintext environment variables is to centralize secret access using the 1Password CLI. This approach securely retrieves passwords and API keys directly from your 1Password vault at runtime, preventing sensitive credentials from being stored in files.

How do I configure and verify the 1Password CLI for automated secret retrieval?

Configure the 1Password CLI by setting your service account token as an environment variable, then run the `op whoami` command. This verifies the authentication session and confirms the service account is ready for automated password and secret retrieval.

Does this 1Password CLI integration require any external dependencies?

No, this 1Password CLI integration requires no external dependencies. It operates entirely through provided scripts, relying solely on the 1Password CLI's secure APIs and a valid service account token to manage and retrieve secrets.

Why should I use 1Password CLI for security automation instead of static secret files?

You should use 1Password CLI for security automation to centralize and secure sensitive data handling. Unlike static secret files, it dynamically retrieves API keys and passwords through secure APIs, preventing credential exposure and simplifying access across interactive sessions and pipelines.

Related Skills