
Handle Secrets
- 2 repo stars
- Updated July 24, 2026
- cboone/agent-harness-plugins
Best practices for handling user-provided secrets in CLI tools: secure input, credential storage, secret masking, and language-specific libraries.
About
Handle-secrets is a guide for safely handling user-provided secrets in CLI tools. It covers secure input methods, credential storage (such as the OS keychain), masking secrets in logs and output, and the right language-specific libraries to use. Aimed at developers building CLIs that must accept and persist credentials without leaking them.
- Secure secret input methods
- Keychain credential storage
- Secret masking in output
- Language-specific libraries
Handle Secrets by the numbers
- Data as of Jul 25, 2026 (Skillselion catalog sync)
/plugin marketplace add cboone/agent-harness-plugins/plugin install handle-secrets@agent-harness-pluginsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| repo stars | ★ 2 |
|---|---|
| Last updated | July 24, 2026 |
| Repository | cboone/agent-harness-plugins ↗ |
What it does
Best practices for handling user-provided secrets in CLI tools: secure input, credential storage, secret masking, and language-specific libraries.
README.md
Handle Secrets
Best practices for handling user-provided secrets in CLI tools.
Type: Skill
Trigger: /handle-secrets
Installation
See the marketplace install instructions.
What It Does
Provides security best practices for accepting secrets (API keys, tokens, passwords) from users in CLI tools. Covers the security hierarchy of input methods, credential storage patterns with OS keychains and config files, secret masking in output, and language-specific libraries for Rust, Go, Python, Node.js, and Ruby.
Organized into a quick-review checklist and deep-dive references by topic.
Usage
/handle-secrets
The skill also activates automatically when Claude Code detects work involving user-provided secrets in CLI tools.
Examples
- Building a CLI that accepts an API key: the skill provides the secure input hierarchy
- "review this code for secret handling": checks against the security checklist
- "/handle-secrets": loads the full best practices guide explicitly
See Also
- Write Go Code: Go-specific libraries for credential handling
- Set-Up Secret Scanning: prevent secrets from being committed to repositories
- All plugins