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 vault-helmgit 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-helm)<a href="https://agentmods.dev/skills/aidas-dev/k8s-agent-skills/vault-helm"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/vault-helm/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-helm"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/vault-helm.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.00044 | $0.02081 |
| Opus 5 | $0.00022 | $0.01040 |
| Sonnet 5 | $0.00009 | $0.00416 |
| Haiku 4.5 | $0.00004 | $0.00208 |
Grade A, and why
vault-helm scanned grade A with 0 findings 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vault (Helm)
Overview
HashiCorp Vault provides secret management, encryption as a service, and identity-based access. This skill covers deploying Vault on Kubernetes with the official Helm chart in HA+Raft mode.
Latest: chart 0.33.0, app 2.0.2.
No CRDs. Controlled via Helm values and server config.
⚠️ Prefer OpenBao for self-hosting — OpenBao (v2.6.x, MPL-2.0, Linux Foundation) is a drop-in-compatible Vault fork with namespaces (secure multi-tenancy + namespace sealing) built into the open-source build — a feature Vault gates behind paid Enterprise (note: replication is NOT yet in OpenBao). Its killer feature for home/unstable clusters is Static Key Auto-Unseal (
seal "static", built-in, no KMS): a 32-byte AES-256-GCM key injected from your secret store at boot, so nodes unseal themselves after any restart/power loss — Vault OSS auto-unseal only works via cloud KMS or a transit peer, otherwise you're typing Shamir keys after every reboot. Thehashicorp/vaultHelm chart and this skill's values mostly apply to OpenBao deployments too (image swap + config parity; verify engine/auth parity before committing). See thevaultrouter for the full comparison.
Architecture (HA+Raft)
3 Vault pods (StatefulSet)
→ Raft integrated storage (consensus, no external DB)
→ Active node handles requests
→ Standby nodes forward to active
→ Service registration via K8s API
Vault OSS supports:
- Raft HA consensus (3+ nodes)
- Kubernetes auth method
- KV v2 secrets engine
- ACL policies
- Auto-unseal (KMS, Transit)
- Prometheus metrics
Vault OSS does not support:
- Namespaces (enterprise)
- Disaster Recovery replication (enterprise)
- Sentinel policies (enterprise)
- SAML auth (enterprise)
- OTLP traces (enterprise)
Deployment (Flux HelmRelease)
apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
name: vault
namespace: vault
spec:
chart:
spec:
chart: vault
sourceRef:
kind: HelmRepository
name: hashicorp
version: 0.33.0
values:
global:
tlsDisable: true
injector:
enabled: false
server:
ha:
enabled: true
raft:
enabled: true
config: |
ui = true
listener "tcp" {
address = "0.0.0.0:8200"
tls_disable = true
}
storage "raft" {
path = "/vault/data"
}
service_registration "kubernetes" {}
telemetry {
prometheus_retention_time = "12h"
disable_hostname = true
}
service:
enabled: true
auditStorage:
enabled: false
ui:
enabled: true
serviceType: ClusterIP
dataStorage:
size: 10Gi
storageClass: ceph-block
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 · 243 lines · 44 tokens per session scan A 125d33944917
vault-helm is a skill published in the GitHub repository Aidas-dev/k8s-agent-skills (2 stars, last pushed 29d ago), licensed MIT. It adds 44 tokens to every session and 2,081 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. 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.