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 hamzabellouch/agent-skills --skill hashicorp-vault-secret-managementgit clone --depth 1 https://github.com/hamzabellouch/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/hamzabellouch/agent-skills/hashicorp-vault-secret-management)<a href="https://agentmods.dev/skills/hamzabellouch/agent-skills/hashicorp-vault-secret-management"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/hashicorp-vault-secret-management/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/hamzabellouch/agent-skills/hashicorp-vault-secret-management"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/hashicorp-vault-secret-management.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.00048 | $0.02396 |
| Opus 5 | $0.00024 | $0.01198 |
| Sonnet 5 | $0.00010 | $0.00479 |
| Haiku 4.5 | $0.00005 | $0.00240 |
Grade A, and why
hashicorp-vault-secret-management 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 9d 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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HashiCorp Vault Secrets Management & Lifecycle Architecture
Overview
This skill provides production-grade templates, HCL policy configurations, and client SDK implementations for enterprise secret management via HashiCorp Vault. It eliminates static credentials through short-lived dynamic credentials, automated rotation engines, and identity-based access control.
1. Zero-Trust Secrets Architecture
- Eliminate Static Long-Lived Secrets: Move away from hardcoded API keys and static database passwords. Leverage Vault dynamic engines (AWS IAM, Database, PKI) that issue credentials with short Time-To-Live (TTL).
- Strict Principle of Least Privilege (PoLP): Vault ACL policies must explicitly follow default-deny semantics. Path access is granted strictly based on workload identity (Kubernetes ServiceAccount, AWS IAM role, AppRole).
- Automated Secret Leasing & Renewal: Applications must handle lease expiration, dynamic token renewal, and graceful re-authentication without downtime.
- Encryption in Transit & at Rest: Force TLS 1.3 for all client communications; ensure Vault storage backends (Raft Integrated Storage) utilize AES-GCM 256-bit envelope encryption.
2. Dynamic Secret Rotation & Access Lifecycle
[ Application / Pod ]
│ 1. Authenticate via ServiceAccount / AppRole
▼
[ Vault Server / Agent ]
│ 2. Issue short-lived Token (TTL: 1h)
│ 3. Request Dynamic DB Credentials (TTL: 15m)
▼
[ Database Engine ] ──▶ Generates ephemeral user (e.g., v-approle-user-abc-123)
| Lifecycle Event | Mechanism | Standard TTL / Frequency |
|---|---|---|
| Authentication | Kubernetes ServiceAccount / AppRole | Token TTL: 1 Hour (Explicit Max TTL: 12 Hours) |
| KV-v2 Secrets | Soft delete / Versioning / Metadata audit | Version retention: 10 versions max |
| Dynamic DB Passwords | Vault DB Engine (postgresql-database-plugin) |
Lease TTL: 15-30 Minutes; Auto-revoked on expiry |
| PKI TLS Certificates | Vault PKI Secret Engine | Cert TTL: 24 Hours; Managed via Cert-Manager / Vault Agent |
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.
- 9d ago First seen · 291 lines · 48 tokens per session scan A 4cfbe627b424
hashicorp-vault-secret-management is a skill published in the GitHub repository hamzabellouch/agent-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 2,396 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
shipping-and-launch
Prepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
opa-policies
Write OPA/Gatekeeper and Kyverno admission policies for Kubernetes security guardrails.
cost-optimization
Identify and reduce cloud infrastructure costs — right-sizing, reserved capacity, waste detection, tagging for cost attribution.
drift-detection
Detect, classify, and automate Terraform drift detection in CI — scheduled plans, drift metrics, cloud-native audit log correlation.
dns-management
DNS management for Kubernetes — CoreDNS tuning, external-dns automation, split-horizon DNS, and bare-metal DNS design.
tls-termination
Configure TLS termination with cert-manager — Let's Encrypt, internal CA via Vault PKI, wildcard certs, mTLS between services.