Individual skill
paladin-import
Bulk-import credentials into the Paladin vault from .env files, CSV/JSON exports, Bitwarden, or 1Password — or discover where credentials live. Returns names/kinds/counts only; secret values never enter the agent's context.
custodian/bundled_skills/security/paladin-import/SKILL.md
Source commit 491f40facf8710ba747b303e8ebf7d4c545f2137
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Local scripts
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 120
- Repository last updated
- Aug 22, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-governance Repository topic
- ai-agents Repository topic
- ai-safety Repository topic
- credentials Repository topic
- policy-as-code Repository topic
- python Repository topic
- spend-controls Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,589 bytesSKILL.mdcore · 3,589 bytesSKILL.mdcore · 3,589 bytesscripts/execute.pyruns · 4,982 bytes
Read excerpt
# Paladin Import (bulk credential onboarding)
Move credentials out of plaintext and into the encrypted Paladin vault, in
bulk, from three kinds of sources — without the secret values ever passing
through your (the agent's) context. You see names, kinds, and counts; the
values flow directly from the source into AES-256-GCM inside the tool's
process.
## Quick Reference
| Action | Invocation |
|--------|------------|
| Find where credentials live (report-only) | `source=discover` |
| Import a .env file | `source=env, path=/path/to/.env` |