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 agentmods add skills/ylz201/keyvault/secrets-managernpx skills add ylz201/keyvault --skill secrets-managergit 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/secrets-manager)<a href="https://agentmods.dev/skills/ylz201/keyvault/secrets-manager"><img src="https://agentmods.dev/badge/skills/ylz201/keyvault/secrets-manager.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 | $0.00033 | $0.00759 |
| Opus 5 | $0.00016 | $0.00380 |
| Sonnet 5 | $0.00007 | $0.00152 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade B, and why
secrets-manager 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 4d 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.
| Master Key | `~/.keyvault/master.key` (chmod 600) | How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KeyVault — Secrets Manager for AI Agents
When you (an AI agent) need to handle API keys, tokens, or other sensitive credentials in any project, you MUST use KeyVault.
Installation
# Install from GitHub
pip install git+https://github.com/ylz201/keyvault.git
# Or with MCP Server support
pip install "keyvault-ai[mcp] @ git+https://github.com/ylz201/keyvault.git"
Verify installation:
keyvault info
⛔ Rules
- ❌ NEVER create
.envfiles to store secrets - ❌ NEVER hardcode API keys in source code
- ❌ NEVER commit secrets to git
- ✅ ALWAYS use
keyvaultCLI or SDK to manage keys
CLI Commands
keyvault set KEY VALUE # Save a secret (global)
keyvault set KEY VALUE --project NAME # Save per-project override
keyvault get KEY # Get (masked)
keyvault get KEY --unmask # Get (full value)
keyvault list --all # List all secrets
keyvault delete KEY # Delete a secret
keyvault import .env # Bulk import from .env file
keyvault export > .env # Export as .env format
keyvault inject -- python script.py # Run command with all secrets as env vars
Python SDK
from keyvault import get_secret, set_secret
# Get a secret (auto-fallback to os.environ if vault not found)
api_key = get_secret("OPENAI_API_KEY")
# Or just use standard env vars (works when launched via `keyvault inject`)
import os
api_key = os.environ.get("OPENAI_API_KEY")
MCP Server Setup
To enable AI agents (Claude, Gemini, etc.) to manage secrets via MCP protocol:
1. Start the MCP server manually
python -m keyvault.mcp_server
2. Configure in Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"keyvault": {
"command": "python",
"args": ["-m", "keyvault.mcp_server"]
}
}
}
3. Available MCP Tools
| Tool | Description |
|---|---|
secrets_list |
List all stored key names (values hidden) |
secrets_get |
Retrieve a specific secret value |
secrets_set |
Store a new secret |
secrets_delete |
Remove a secret |
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.
- 4d ago First seen · 111 lines · 33 tokens per session scan B 4f6d1367abcf
secrets-manager is a skill published in the GitHub repository ylz201/keyvault (0 stars, last pushed 6mo ago), licensed MIT. It adds 33 tokens to every session and 759 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…