Retrieve and inject 1Password secrets into Hermes command workflows.
npx skills add https://github.com/MarbleSodas/Mavis --skill 1password-marblesodas
Please help me install this Agent Skill. Skill: 1password Source: https://github.com/MarbleSodas/Mavis/tree/main/optional-skills/security/1password Command: npx skills add https://github.com/MarbleSodas/Mavis --skill 1password-marblesodas
This Skill helps you avoid insecure plaintext secrets by managing credentials through 1Password CLI so you can safely run commands that need sensitive data without exposing it in logs or files.
op read with op://Vault/Item/field references.op inject to generate runtime-ready configuration from templates that contain 1Password placeholders.op run to set secret-backed environment variables for a single command execution.OP_SERVICE_ACCOUNT_TOKEN, and self-hosted Connect server credentials.Configure the service account token by setting OP_SERVICE_ACCOUNT_TOKEN in ~/.hermes/.env, then run op read "op://app-prod/db/password" to fetch the secret for use in subsequent Hermes commands.
High-intent search queries and answers about installing and using this skill.
You can inject secrets into config templates using `op inject` to replace 1Password placeholders with runtime-ready values. This prevents sensitive data from being exposed in logs or files during command workflows.
To retrieve a secret for local development, use the `op read` command with an `op://Vault/Item/field` reference. This securely fetches the exact credential needed for your Hermes command workflows.
Yes, you can use `op run` to set secret-backed environment variables for a single command execution. This allows the command to access credentials securely without leaving persistent plaintext environment variables.
Yes, 1Password CLI supports non-interactive service accounts by setting the `OP_SERVICE_ACCOUNT_TOKEN` environment variable. This enables secure secret retrieval during headless CI execution without manual authentication.
Besides interactive desktop app integration with tmux-stable auth context, you can authenticate using a service account token via `OP_SERVICE_ACCOUNT_TOKEN` or self-hosted Connect server credentials for headless and automated environments.
You need the 1Password CLI installed and a configured authentication context, such as setting `OP_SERVICE_ACCOUNT_TOKEN` in your environment. This provides the necessary access to retrieve secrets from your vaults.
Quill-AgentManage and inject secrets via 1Password CLI for CI/CD environments.
gqf2008Manage secrets with the 1Password CLI across Hermes workflows.
tjboudreauxAutomate secrets management and vault operations with the 1Password CLI.
zangjeicyManages credentials and secrets via the 1Password CLI for secure injection.