vault-unseal skillA
vault-unseal is agent-read markdown (skill) from runxhq/runx: Plan or execute a scoped, time-bounded vault-unseal request through any compatible vault binding, returning only opaque handle metadata and provider readback..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Vault Unseal Execute one least-privilege request to make an opaque secret reference available to one principal for one purpose, scope, and short access window. The default `execute` runner sends that exact request through a configured vault adapter after approval and independently reads the resulting handle metadata. `vault-unseal` remains the explicit plan-only runner. Neither runner retrieves or reveals secret material. Use it when a later workload needs a bounded secret handle and the request must pass a human approval and real vault adapter. Do not use it as a secret store, credential loader, environment-file parser, or way to put secret values into an agent context. ## How it works 1. Bind the opaque secret reference to the requesting principal, declared purpose, allowed scope, and requested time window. 2. Validate that the reference is opaque and the TTL is between one minute and one hour. 3. Reject raw secret-shaped input, ambiguous principals, broad purpose, or unbounded scope. 4. Emit an approval-ready request and exact provider handoff. 5. With `execute`, request approval for that exact plan, invoke …
Read the whole file at its exact version.
How to install
mdr add runxhq/runx/vault-unseal@git:20260808.8b7af2amdr add runxhq/runx/vault-unseal@sha256:8165f75a60026e39Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_qizj53t7ucglymjc)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260808.8b7af2a latest | 2026-08-08 | 8b7af2a | 3,287 B | A | view · diff |
| git:20260723.6e5370b | 2026-07-23 | 6e5370b | 3,161 B | A | view · diff |
| git:20260715.8d8fc90 | 2026-07-15 | 8d8fc90 | 6,637 B | A | view · diff |
| git:20260715.8644be9 | 2026-07-15 | 8644be9 | 6,648 B | A | view · diff |
| git:20260614.b6a05c8 | 2026-06-14 | b6a05c8 | 6,664 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3287 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
runxhq/runx · 93 stars · license Apache-2.0 · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qizj53t7ucglymjc GET https://markdownregistry.com/api/v1/resolve?ref=runxhq/runx/vault-unseal GET https://markdownregistry.com/api/v1/blob/8165f75a60026e399d2a1548e4e8fcf0147eeeeb0dee18b171b7a6b9b422b89e
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.