penguin-cli

# 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 gateways resell vendor models under their upstream ids and a wrong guess would send the key to another vendor's endpoint. `--model-id` takes the provider's upstream model id (what the API expects) and is persisted as the entry's request id, so it reaches the API unchanged; `--provider` na...