_get-secret

Retrieve Bitwarden vault secrets into shell variables without exposing them to AI context.

34|6|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/flavien-ia/hypervibe-harness --skill get-secret
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: _get-secret
Source: https://github.com/flavien-ia/hypervibe-harness/tree/main/skills/_get-secret
Command: npx skills add https://github.com/flavien-ia/hypervibe-harness --skill get-secret

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, and includes scripts (resource) components.

What problem does it solve?

This skill solves the security risk of hardcoding sensitive API keys or credentials in scripts by providing a standardized, secure interface to read secrets from a Bitwarden vault without exposing them to the AI context.

Core Features & Use Cases

  • Secure Credential Access: Reads secrets directly into shell variables, ensuring sensitive values never appear in logs, tool outputs, or the AI's conversation history.
  • Automated Vault Orchestration: Automatically handles vault locking, session expiration, and missing item prompts through a unified, non-technical interface.
  • Use Case: When a project requires a Cloudflare API token or an Anthropic key, this skill ensures the key is retrieved securely from the user's vault and passed directly to the required CLI tool.

Quick Start

Use the get-secret skill to securely retrieve the required API token from your vault for the current service operation.

Frequently Asked Questions about _get-secret

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

FAQPage Schema
How do I retrieve secrets from a Bitwarden vault without exposing credentials in the AI context?

You can retrieve secrets from a Bitwarden vault using a secure shell-based pattern that passes sensitive credentials directly into shell variables, preventing data leakage into logs or AI conversation history.

How do I automate vault unlocking and session renewal for credential retrieval in automated workflows?

Automated vault orchestration handles vault unlocking, session expiration, and missing item prompts through a unified interface, ensuring continuous credential access during automated workflows without manual intervention.

Do I need Node.js and the Bitwarden CLI to manage secrets securely in shell environments?

Yes, you need Node.js and the Bitwarden CLI installed to perform secure, non-persistent secret injection into shell environments for automated credential management.

What is the best way to inject API keys into CLI tools without hardcoding credentials in scripts?

The best way to inject API keys is by reading secrets directly from a Bitwarden vault into shell variables, ensuring sensitive values are passed securely to required CLI tools without hardcoding.

Can I use this approach to securely manage Cloudflare API tokens or Anthropic keys for projects?

Yes, when a project requires a Cloudflare API token or an Anthropic key, this approach ensures the key is retrieved securely from your vault and passed directly to the required CLI tool.

Why does passing credentials through shell environments prevent data leakage in automation?

Passing credentials through shell environments prevents data leakage because sensitive values are injected non-persistently into shell variables, ensuring they never appear in logs, tool outputs, or AI conversation history.