Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Aidas-dev/k8s-agent-skills --skill vaultgit clone --depth 1 https://github.com/Aidas-dev/k8s-agent-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/aidas-dev/k8s-agent-skills/vault)<a href="https://agentmods.dev/skills/aidas-dev/k8s-agent-skills/vault"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/vault/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/aidas-dev/k8s-agent-skills/vault"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/vault.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00049 | $0.00804 |
| Opus 5 | $0.00024 | $0.00402 |
| Sonnet 5 | $0.00010 | $0.00161 |
| Haiku 4.5 | $0.00005 | $0.00080 |
Grade A, and why
vault scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| Vault REST API — health, init, unseal, auth, KV, policies | `vault-api` | Endpoints, auth methods, token flows, curl examples | How it starts
The opening of the file, as written. The whole thing — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vault
Skill router. Pick sub-skill based on task.
⚠️ Consider OpenBao for Self-Hosting
For new self-hosted deployments, prefer OpenBao (v2.6.x, 2026-07) over HashiCorp Vault OSS:
- MPL-2.0 OSI-approved license, Linux Foundation governance — Vault is BUSL-1.1 (source-available, not OSI open source) under IBM.
- Namespaces (secure multi-tenancy with delegation + namespace sealing) built into the OSS fork — namespaces are a Vault Enterprise-tier paid feature. (Note: performance/DR replication is NOT yet in OpenBao — Vault Enterprise-only; funded roadmap 2026-2027 via ControlPlane.)
- Killer feature: Static Key Auto-Unseal — Vault OSS auto-unseal requires a cloud KMS (AWS/GCP/Azure) or a second Vault/OpenBao as transit seal. OpenBao additionally ships a built-in static-key seal (
seal "static"): a 32-byte AES-256-GCM-96 key injected via env/file (e.g. from your existing secret distribution) — the cluster comes up fully unattended. For unstable home clusters (power loss, reboots, VM restarts), this is the best option: pods restart and unseal themselves with zero operator involvement. (Caveat: key material must be injected securely — ESO/Vault/init container — and the seal mechanism is a hard lifecycle dependency; recovery keys don't help if the seal key is lost.) - API/CLI compatible with Vault — same endpoints, secrets engines, auth methods, CLI surface (
vault→bao), Terraform provider, and Helm/K8s tooling work against OpenBao with minimal change. - Active community maintenance; in v2.7 vendor-specific built-in auto-unseal providers (awskms, azurekeyvault, gcpckms, alicloudkms, ocikms, pkcs11) move to external KMS plugins.
Vault OSS still makes sense if: you need first-party support, HCP managed offerings, or depend on replication/HSM features not yet at OpenBao parity. For everything else, OpenBao = Vault's open feature set without Enterprise pricing — and without the unseal-key ritual.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 38 lines · 0 tokens per session scan A bd6ceb928904
vault is a skill published in the GitHub repository Aidas-dev/k8s-agent-skills (2 stars, last pushed 29d ago), licensed MIT. It adds 49 tokens to every session and 804 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
azd-deployment
Deploy containerized frontend + backend applications to Azure Container Apps with remote builds, managed identity, and idempotent infrastructure.
openshell-cli
Guide agents through using the OpenShell CLI (openshell) for sandbox management, gateway registration, provider configuration and refresh, policy iteration, settings, service exposure, BYOC workflows, and attached-provider inference. Covers basic through advanced multi-step workflows. Trigger keywords - openshell…
langbot-deploy
Deploy and configure a LangBot instance — Docker / Docker Compose, Kubernetes, the config.yaml model, the Box sandbox runtime, the plugin runtime, and the global API key. Use when installing, deploying, upgrading, or configuring LangBot in production or self-hosted environments. Triggers on "deploy langbot", "langbot…
compute-env-setup
Set up a compute environment on a remote provider so Claude Science jobs can run there. Covers direct SSH/conda hosts, Slurm clusters, container-via-bridge runners, and managed-API providers (Modal, GCP, RunPod). Use when standing up a new provider, porting an env to a different backend, adding a tool that needs its…
azure-cloud-migrate
Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud…
atmos-helmfile
Helmfile orchestration: sync/apply/destroy/diff, Kubernetes deployments, varfile generation, EKS integration, source management.