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 skills add KeyArgo/custodian-kernel --skill paladin-importgit clone --depth 1 https://github.com/KeyArgo/custodian-kernelWrote 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/keyargo/custodian-kernel/paladin-import)<a href="https://agentmods.dev/skills/keyargo/custodian-kernel/paladin-import"><img src="https://agentmods.dev/badge/skills/keyargo/custodian-kernel/paladin-import.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 3 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 30 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 31 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 45 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 33 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00053 | $0.00939 |
| Opus 5 | $0.00026 | $0.00469 |
| Sonnet 5 | $0.00011 | $0.00188 |
| Haiku 4.5 | $0.00005 | $0.00094 |
Grade A, and why
paladin-import scanned grade A with 0 findings 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 5d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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 |
| Import every .env under a directory | source=env, path=/dir, recursive=true |
| Import a password-manager CSV export | source=csv, path=/path/to/export.csv |
| Import a JSON secrets dump | source=json, path=/path/to/secrets.json |
| Import from Bitwarden | source=bitwarden, search="api key" |
| Import from 1Password | source=1password, from_vault="Main" |
| Preview without writing | any of the above + dry_run=true |
CSV covers Chrome, Firefox, Bitwarden, LastPass, 1Password, and KeePass exports
offline (no CLI needed) — the value column is auto-detected from the header.
JSON accepts a flat {"NAME": "value"} object or an array of {name, value}.
Arguments
source(required):discover|env|csv|json|bitwarden|1passwordpath: forenv— a .env file or a directory to scan; forcsv/json— the filerecursive: forenv—trueto scan subdirectoriespattern: forenv— filename pattern (default.env*)search: forbitwarden/1password— only matching itemsfolder: forbitwarden— only items in this folderfrom_vault: for1password— only items in this 1Password vaultprofile: paladin profile to import into (defaultdefault)dry_run:trueto preview; nothing is writtenoverwrite:trueto replace already-vaulted names (default: skip them)
The intended agent workflow
source=discover— see what exists (env files, shell-rc export NAMES, whetherbw/opare installed and unlocked). Nothing is imported.- Relay the discovery to the human; let them choose sources.
- Import each chosen source (use
dry_run=truefirst if unsure). - Report the counts and any
git-tracked/git-unignoredflags — those credentials were exposed to git and should be rotated, not just vaulted.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 79 lines · 53 tokens per session scan A f6a0a43a3120
paladin-import is a skill published in the GitHub repository KeyArgo/custodian-kernel (118 stars, last pushed 17d ago), licensed MIT. It adds 53 tokens to every session and 939 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
gnt-check-action
Check a side-effectful action against this organization's approved gnt rules before taking it, and stop on a blocked or needshuman verdict.
agt-policy-authoring
Create and validate a minimal AGT Copilot CLI policy tailored to the repository being inspected.
requirements-elicitation
Turns vague intent into testable requirements.
refactoring
Safe, test-backed code restructuring in small steps.
using-git-worktrees
Isolates each task in its own git worktree off main.
cis-aws-foundations-2.12
Ensure access keys are rotated every 90 days or less.