penguin-cli
Manage model API keys, default models and per-agent vault secrets with the penguin CLI.
npx skills add Prism-Shadow/penguin-harness --skill penguin-cli --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Penguin CLI The `penguin` CLI manages model credentials, default models and per-agent vault secrets. Its primary job is model configuration: `penguin config model add` registers a model and `penguin config model list` shows the models currently available. Configuration goes through the CLI only — never read or hand-edit the underlying hidden files. ## Before you start If the user's message only invokes this skill (e.g. "use penguin-cli skill") without a concrete request, ask the user what they want to configure. Do not run any command until the goal is clear. ## Models Add or update a model (upsert by the `(provider, model_id)` pair; re-run with more options to amend an entry): ```bash penguin config model add --provider <group> --model-id <upstream_id> [--api-key <key>] [--base-url <url>] \ [--client-type <type>] [--context-window <n>] [--max-tokens <n>] [--vision | --no-vision] \ [--price-cache-read <n>] [--price-cache-write <n>] [--price-output <n>] \ [--project-id <id>] [--root <dir>] [--set-default] ``` - A model is identified by the `(provider, model_id)` pair, so `--provider` and `--model-id` are **both required** — the group is never inferred from the model id, because ga
- Before you start
- Models
- Vault (per-agent secrets)
- Language
- Running agents
- Storage
penguin config model add --provider <group> --model-id <upstream_id> [--api-key <key>] [--base-url <url>] \ penguin config model default --model-id <upstream_id> --provider <group> [--root <dir>] # set the project default model penguin config model vision --model-id <upstream_id> --provider <group> [--root <dir>] # set the project vision model (reads images for text-only sessions) penguin config model list [--root <dir>] # list models; api_key is shown masked penguin config vault set --key <NAME> --value <value> [--project-id <id>] [--agent-id <id>] [--root <dir>] penguin config vault list [--project-id <id>] [--agent-id <id>] [--root <dir>] # values are shown masked penguin config vault remove --key <NAME> [--project-id <id>] [--agent-id <id>] [--root <dir>] penguin config lang <en|zh> # persist the CLI language via PENGUIN_LANG in your shell rc
What does the penguin-cli skill do?
Manage model API keys, default models and per-agent vault secrets with the penguin CLI.
How do I install it?
Run `npx skills add Prism-Shadow/penguin-harness --skill penguin-cli --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Prism-Shadow/penguin-harness, a repository with 473 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
