pangram-checklisted

# Pangram check A final sweep over a finished document. Pangram scores the text in windows of a few hundred words and reports which parts read as machine-drafted, so a long document gets a passage-by-passage answer. ```bash node scripts/pangram-check.mjs path/to/file.md ``` Full flag list and config file in [references/configuration.md](references/configuration.md). Field meanings and how to read a verdict in [references/reading-results.md](references/reading-results.md). ## Confirm before spending a call Every run costs the user money and sends their writing to a third party. Before the first call of a session: 1. Name the file that is about to go out. 2. Give the word count and the billable estimate. `--dry-run` prints both and sends nothing. 3. Wait for a yes. This skill sets `disable-model-invocation: true`. It runs when a user asks for it by name, and never as a step some other task decided to take. A skill that drafts or rewrites text may mention it and stop there. ## Check the key first On a machine that has not run this before: ```bash node scripts/pangram-check.mjs --check-key ``` That checks the key against `GET /models` and spends no detection call. With no key found, the script prints where it looked and how to store one. Pass that message on as it stands. Never print, echo or paste the key itself, and never put it in a shell command the user will see. The key is read from `$PANGRAM_API_KEY`, then `$PANGRAM_ENV_FILE`, then `~/.config/pangram/.env`, the