Borrowing it
Nothing to install: this file belongs to ylz201/keyvault. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ylz201/keyvault/main/.agents/skills/keyvault-skill/SKILL.mdgit clone --depth 1 https://github.com/ylz201/keyvaultWrote 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/ylz201/keyvault/keyvault-skill)<a href="https://agentmods.dev/skills/ylz201/keyvault/keyvault-skill"><img src="https://agentmods.dev/badge/skills/ylz201/keyvault/keyvault-skill.svg" alt="Measured on agentmods" 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.00036 | $0.01804 |
| Opus 5 | $0.00018 | $0.00902 |
| Sonnet 5 | $0.00007 | $0.00361 |
| Haiku 4.5 | $0.00004 | $0.00180 |
Grade B, and why
keyvault-skill 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 6d 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.
keyvault export > .env && chmod 600 .env How it starts
The opening of the file, as written. The whole thing — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KeyVault - Complete Usage for Agents
When you (an AI agent) need to handle API keys, tokens, or credentials, use KeyVault instead of plaintext .env files or hardcoded values.
Mandatory Rules
- NEVER create plaintext secret files unless user explicitly requests export.
- NEVER hardcode API keys in source code.
- NEVER commit exported secret files to git.
- ALWAYS prefer project-scoped secrets (
--project) over global secrets. - ALWAYS use least-privilege injection (
inject --no-global --key ...) for command execution.
Installation
# Core package
pip install git+https://github.com/ylz201/keyvault.git
# With MCP support
pip install "keyvault-ai[mcp] @ git+https://github.com/ylz201/keyvault.git"
# Verify environment and storage backend
keyvault info
Complete CLI Reference
set - create/update a secret
keyvault set KEY [VALUE] [--project PROJECT] [--desc TEXT] [--stdin]
Examples:
# hidden prompt (recommended)
keyvault set OPENAI_API_KEY
# value via argument
keyvault set OPENAI_API_KEY sk-xxx
# value from stdin (safe for scripts)
printf 'sk-xxx' | keyvault set OPENAI_API_KEY --stdin
# project-scoped override
keyvault set OPENAI_API_KEY sk-proj --project myapp --desc "OpenAI for myapp"
get - read a secret
keyvault get KEY [--project PROJECT] [--unmask]
Examples:
keyvault get OPENAI_API_KEY
keyvault get OPENAI_API_KEY --project myapp
keyvault get OPENAI_API_KEY --project myapp --unmask
list - list stored secrets (metadata only)
keyvault list [--project PROJECT] [--all]
Examples:
keyvault list
keyvault list --project myapp
keyvault list --all
delete - remove a secret
keyvault delete KEY [--project PROJECT] [--force]
Examples:
keyvault delete OPENAI_API_KEY --project myapp
keyvault delete OPENAI_API_KEY --force
import and export - dotenv compatibility
keyvault import FILEPATH [--project PROJECT]
keyvault export [--project PROJECT] [--output FILE]
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.
- 6d ago First seen · 279 lines · 36 tokens per session scan B 32be9769641d
keyvault-skill is a skill published in the GitHub repository ylz201/keyvault (0 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 1,804 once invoked, about $0.0002 per session on Opus 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…