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 abdullahkhawer/devops-skills --skill vault-cligit clone --depth 1 https://github.com/abdullahkhawer/devops-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/abdullahkhawer/devops-skills/vault-cli)<a href="https://agentmods.dev/skills/abdullahkhawer/devops-skills/vault-cli"><img src="https://agentmods.dev/badge/skills/abdullahkhawer/devops-skills/vault-cli/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/abdullahkhawer/devops-skills/vault-cli"><img src="https://agentmods.dev/badge/skills/abdullahkhawer/devops-skills/vault-cli.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.00030 | $0.00874 |
| Opus 5.5 | $0.00012 | $0.00350 |
| Sonnet 5.5 | $0.00006 | $0.00175 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade B, and why
vault-cli scanned grade B 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 23d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
Save the resulting token to the corresponding token file (see table above), `chmod 600`. Never share credential file contents with the assistant. How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HashiCorp Vault CLI Skill
Use the address table and rules below when constructing all vault commands.
Configuration
Update the table below with your Vault cluster addresses before using this skill:
| Environment | VAULT_ADDR | Token File |
|---|---|---|
| Production | https://<your-vault-prod-addr>:8200 |
~/.vault/prod.token |
| Staging / Non-Prod | https://<your-vault-staging-addr>:8200 |
~/.vault/staging.token |
If the target environment is unclear, ask the user before running any command.
Prerequisites (one-time setup by user)
If vault is not installed or not authenticated, inform the user that setup is required and ask them to complete the following steps manually. Do not perform these steps yourself.
brew install vault
vault login -address=<VAULT_ADDR>
Save the resulting token to the corresponding token file (see table above), chmod 600. Never share credential file contents with the assistant.
Command Format
Always set VAULT_ADDR and VAULT_TOKEN explicitly per command — never rely on shell-exported environment variables that could leak into other sessions:
VAULT_ADDR=<vault-addr> VAULT_TOKEN=$(cat <TOKEN_FILE>) vault <command>
Available Commands
Read-only (safe, no confirmation needed)
| Command | Description |
|---|---|
vault status |
Show seal/HA status |
vault secrets list |
List enabled secrets engines |
vault list <path> |
List keys at a path (not the secret values) |
vault kv metadata get <path> |
Show a KV secret's metadata (versions, timestamps) — not its value |
vault policy list / vault policy read <name> |
List or show policies |
vault auth list |
List enabled auth methods |
vault token lookup |
Show info about the current token (not other tokens) |
Mutating operations (confirm with user before running)
| Command | Description |
|---|---|
vault kv put <path> <data> |
Write/update a secret value |
vault policy write <name> <file> |
Create or update a policy |
vault secrets enable <type> |
Enable a new secrets engine |
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.
- 23d ago First seen · 82 lines · 30 tokens per session scan B 18c37d052bfc
vault-cli is a skill published in the GitHub repository abdullahkhawer/devops-skills (8 stars, last pushed 24d ago), licensed Apache-2.0. It adds 30 tokens to every session and 874 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-23.
Other skills, from other repositories
tianji-worker
Use when creating, testing, deploying, invoking, debugging, scheduling, pausing, or rolling back Tianji Workers, or managing their environment variables and shared modules.
docs-manage
Manage the Grounded Docs MCP Server documentation index. Covers scraping and indexing documentation from URLs or local files, refreshing existing indexes with changed content, removing libraries from the index, and compacting the SQLite store. Use when you need to add, update, or delete indexed documentation, or…
fetch-url
Fetch a single URL and convert its content to Markdown. Use when you need to read a web page, documentation page, or API reference without indexing it. The content is returned as plain Markdown text on stdout.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
dokploy-deploy
This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure Dokploy domains", or "look up Dokploy CLI commands".
openship-config
This skill should be used when the user asks to "create openship.json", "configure an OpenShip deployment", "make a repo deployable on OpenShip", or fix "openship config validate" errors.