vault-user · git:20260929.ea52fa8 · 2026-09-29 · sha256 3248fef5f0a2cf2a
vault-user git:20260929.ea52fa8B
Immutable. This exact content never changes and is served at /api/v1/blob/3248fef5f0a2cf2a.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_36kwrqsckfohnkgc/3248fef5f0a2cf2a555181cba92637f8397bbfe351a44e9fa35f76537cf596c1.json
Then /plugin install vault-user@markdownregistry-36kwrqsckfohnkgc in Claude Code. It installs this exact version, the one graded B here, pinned to the commit it was graded at, and leaves it there.
---
name: vault-user
description: Use when checking the health of this rig's HashiCorp Vault or writing, reading, listing, deleting or explaining its secrets.
---
# Vault User
You have access to a HashiCorp Vault instance managed by this rig's environment.
## Connection
- **Address:** `http://127.0.0.1:8200`
- **Token:** `openrig-dev-token`
- **Auth header:** `X-Vault-Token: openrig-dev-token`
Always set the token before making API calls. For curl, use `-H "X-Vault-Token: openrig-dev-token"`.
## Health Check
```bash
curl -s http://127.0.0.1:8200/v1/sys/health | jq .
```
A healthy response has `"initialized": true` and `"sealed": false`.
## Secret Operations
### Write a secret
```bash
curl -s -X POST http://127.0.0.1:8200/v1/secret/data/<path> \
-H "X-Vault-Token: openrig-dev-token" \
-d '{"data": {"key": "value"}}' | jq .
```
### Read a secret
```bash
curl -s http://127.0.0.1:8200/v1/secret/data/<path> \
-H "X-Vault-Token: openrig-dev-token" | jq .
```
The secret value is in `.data.data`.
### List secrets
```bash
curl -s -X LIST http://127.0.0.1:8200/v1/secret/metadata/ \
-H "X-Vault-Token: openrig-dev-token" | jq .
```
List a subdirectory by appending the path: `.../secret/metadata/<prefix>/`.
### Delete a secret
```bash
curl -s -X DELETE http://127.0.0.1:8200/v1/secret/data/<path> \
-H "X-Vault-Token: openrig-dev-token"
```
## Explaining Secrets
When asked to explain the current secret structure, list all paths and summarize what each contains. Use the list endpoint recursively if needed.
## Important Notes
- This is Vault dev mode — all data is in-memory and lost on restart
- The KV secrets engine is mounted at `secret/` by default in dev mode
- Use the `rig env status` command to verify Vault health through OpenRig before direct probing