Stats
Actions
Tags
From secret-vault
Securely store secrets pasted in chat. Use when user mentions giving you a token, API key, password, or secret. Also use when you need to READ a previously stored secret.
How this skill is triggered — by the user, by Claude, or both
Slash command
/secret-vault:secret-vaultThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Secrets are stored in `~/.secrets/` with chmod 600.
Secrets are stored in ~/.secrets/ with chmod 600.
When a user says "use the github token" or "put my API key in X", check ~/.secrets/ first:
ls ~/.secrets/
cat ~/.secrets/<filename>
Common filenames: github_token, anthropic_api_key, aws_access_key, tailscale_auth_key, unknown_token
If the user wants to give you a secret, use /secret for the guided flow, or just tell them to paste it — the UserPromptSubmit hook will catch common patterns automatically.
npx claudepluginhub kyletabor/claude_plugins --plugin secret-vaultSecures Claude Code sessions with nopeek CLI: loads .env secrets without exposing values, stores keys, redacts cloud CLI outputs to prevent API key leaks. Useful for secret and credential safety.
Provides secure environment variable management to prevent secrets exposure in Claude sessions, terminals, logs, or git commits.
Extracts hardcoded secrets from CLAUDE.md, .mcp.json, and project config into gitignored .env file, wires SessionStart hook for auto-loading. Use for 'separate secrets' or 'extract API keys'.