agentsclimarketplace

Redpill vault

Skill h4x3rotab/redpill-vault/skills/redpill-vault

Manages environment variables and credentials for AI tools. API keys, tokens, database URLs, and other secrets are stored in an encrypted vault. Use rv-exec to run commands with secrets injected. The agent never sees secret values or the master key.From its SKILL.md

Install
npx -y skills add h4x3rotab/redpill-vault --skill redpill-vault

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.4 KB, as published. Nobody here has run it

redpill-vault

Secure credential manager for AI tools. Secrets are stored in an encrypted vault and injected into commands via rv-exec.

NEVER run these commands

The following commands are user-only — the agent must NEVER run them:

  • rv approve — only the user can approve a project
  • rv revoke — only the user can revoke approval
  • rv set — only the user can set secret values

If a secret is missing, tell the user to run rv set KEY_NAME themselves.

Setup

./skills/redpill-vault/setup.sh
rv init

After setup, the user must approve the project before secrets can be injected:

rv approve

This is a one-time step per project. The agent cannot run rv approve — only the user can.

Running commands with secrets

Use rv-exec --all to inject all secrets from .rv.json:

rv-exec --all -- <command>

Examples:

rv-exec --all -- npm run deploy
rv-exec --all -- docker push myimage:latest
rv-exec --all -- bash -c 'echo $MY_SECRET'

The --all flag injects all secrets defined in .rv.json. Secrets are resolved from the vault at runtime — the agent never sees the values.

Specific keys

To inject only specific keys:

rv-exec KEY1 KEY2 -- <command>

Generating a .env file

Some commands require a .env file. Use --dotenv:

rv-exec --all --dotenv .env -- phala deploy -e .env

This writes secrets to .env before running and deletes it after.

Adding secrets

Importing from .env

rv import .env

Imports all keys from the file, stores each as a project-scoped secret. Values go directly to the encrypted vault.

To import specific keys: rv import .env GITHUB_TOKEN DATABASE_URL To import as global keys: rv import .env -g

Setting a single secret (user only)

Tell the user to run in their terminal:

rv set KEY_NAME

The agent must NEVER run rv set — it reads secret values from stdin.

Removing secrets

rv rm KEY_NAME
rv rm KEY_NAME -g  # global

.rv.json

{
  "project": "myapp",
  "secrets": {
    "GITHUB_TOKEN": { "description": "GitHub API token" },
    "DATABASE_URL": {}
  }
}

The "project" field is optional — directory name is used if omitted.

Key resolution

For each key, rv-exec checks:

  1. Project-scoped key (PROJECT__KEY) first
  2. Falls back to global key (KEY)

This lets projects override or inherit global credentials.

rv list shows each key's source: [project], [global], or [missing].

Commands

CommandDescription
rv initInitialize project (master key + vault + config)
rv approveApprove project for secret injection (user only)
rv revokeRevoke project approval (user only)
rv import .envImport secrets from .env file
rv listShow secrets with source
rv list -gShow global keys in vault
rv checkVerify all keys exist
rv doctorFull health check
rv set KEYSet a secret (user only, reads from stdin)
rv rm KEYRemove a secret
rv-exec --all -- cmdRun command with all secrets
rv-exec K1 K2 -- cmdRun command with specific secrets

Keep looking

Skills are one crate of 608,475. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.