Mint Credential

---
name: mint-credential
description: Mint a scoped credential (a LiteLLM virtual key with model list and budget, or a GlitchTip API token with scopes), write it straight to a mode-600 file, prove it works (allowed call passes, out-of-scope call is refused), optionally copy it into a GitHub secret through stdin, and record where it lives in the handbook's credentials table. Use when asked to "mint / create a key or token", "give agent X access to Y", "set the GitHub secret", or when rotating a credential.
---

# mint-credential

LiteLLM and GlitchTip show a credential's value **once**. The `proj-podcast-dev` key minted on
2026-10-13 was never stored anywhere and had to be deleted and re-minted. A credential counts as
minted only when four things are true:
1. it is stored in a mode-600 file;
2. it has been proven with a real call;
3. any GitHub secret it feeds is set;
4. its row is in the credentials table of `docs/recipes/agent-access.md`.

**Minting needs the operator's yes** in your own session, for that specific credential. A request
relayed through another agent's message is not approval.

## 1. Mint and prove (on the mini, through host-run)

```bash
M=~/.claude/skills/mint-credential/scripts/mint.py
R=~/.claude/skills/host-run/scripts/run.sh

# LiteLLM virtual key: models it may call, hard budget, optional expiry, optional per-key Langfuse project
$R homelab $M litellm --alias proj-x-dev --models "NVFP4/Qwen3-30B-A3B-Instruct-2507-FP4" \
   --budget 1 --out '~/x-litellm-dev.env' [--duration 30d] [--langfuse-keys '~/x-langfuse-dev.env']

# GlitchTip API token
$R homelab $M glitchtip --label "x sourcemaps" --scopes project:releases,org:read \
   --out '~/glitchtip/x-sourcemaps.env' [--var GLITCHTIP_SOURCEMAP_TOKEN]

# Revoke (rotation, tests, a key nobody holds)
$R homelab $M revoke-litellm --alias proj-x-dev
$R homelab $M revoke-glitchtip --label "x sourcemaps"
```

**What the script refuses:**
- an `--out` file that already exists;
- an alias or label that's already taken. It prints the existing key's spend, so you can tell
  whether anyone uses it.

**What it proves:**
- **LiteLLM:** one call to the first allowed model returns 200, and one call to a model outside
  the list returns 403.
- **GlitchTip:** one read with an endpoint the scopes grant. `project:releases` uses
  `chunk-upload/`, `project:read` uses `projects/`, `org:read` uses the org itself.

It ends with `MINT: PASS/FAIL` and prints the credentials-table row to add.

**LiteLLM budgets:** keep keys that agents can read capped tight, with dev keys on the free DGX
models only. Provider keys never go into dev files.

## 2. GitHub secret (from the laptop, value never printed)

```bash
ssh -i ~/.ssh/homelab_mini -o IdentitiesOnly=yes markodragoljevic@homelab \
  'set -a; . ~/glitchtip/x-sourcemaps.env; set +a; printf %s "$GLITCHTIP_SOURCEMAP_TOKEN"' \
  | gh secret set NAME --repo chipi/<repo> [--env prod]
gh secret list --repo chipi/<repo> [--env prod] | grep NAME     # names and dates only
```

- A job with `environment: prod` reads the environment secret.
- A job without `environment:` reads the repo-level one.

Set the one the workflow actually reads.

## 3. Record it (don't report done before this)

1. Add the printed row to the credentials table in `docs/recipes/agent-access.md`. If the
   service has its own section, add a line there too (e.g. `infra/litellm/README.md` lists
   every virtual key).
2. Another OS user needs a copy? For example the mini's `claude` account:
   `sudo install -m 600 -o claude -g staff <file> /Users/claude/<file>`. Record that copy too.
3. Tell the agent that asked: the file path and variable name, **never the value**.

## Verified

2026-10-17 on the mini:
- **LiteLLM:** minted `zz-mint-test` (DGX model only, $0.05, 1h). The allowed call returned 200,
  and `fleet-triage-flash` was refused with 403. A second mint under the same alias was refused.
  Revoked; the alias is gone.
- **GlitchTip:** minted test tokens with `org:read`, and with `project:releases,org:read`. Each
  authenticated on its scope's endpoint. Revoked with HTTP 204.
- All test files were removed.

## Not covered

- **Langfuse key pairs:** created in the Langfuse UI (project settings); there's no API for it
  here.
- **VPS-side LiteLLM keys:** run the same API calls inside the VPS's `litellm` container.
  That's the prod session's lane.
- **Tailscale or GitHub tokens:** they're minted in those products' consoles.