anti-ailisted

# anti-ai Use the `anti-ai` CLI as the single source of truth for local token accounting and its satirical resource receipts. The CLI already handles log locations, Claude Code streaming deduplication, Codex model attribution, local time zones, and the distinction between exact usage and estimated resources. ## Preflight 1. Check whether the CLI is available: ```bash command -v anti-ai anti-ai --version ``` 2. If it is missing, tell the user and offer this exact installation command: ```bash npm install -g anti-ai ``` Do not silently install global software. 3. If usage is unexpectedly empty, run: ```bash anti-ai doctor ``` Summarize whether each source is available, but do not expose absolute log paths unless the user explicitly asks. ## Choose the right workflow ### Exact data for an Agent Use JSON when the user wants numbers, comparisons, model attribution, or data for another workflow: ```bash anti-ai today --json anti-ai today --date YYYY-MM-DD --source all --json ``` Treat `totals`, `sources`, and `models` as exact local log statistics. Keep the JSON field names unchanged; `--lang` affects only human-readable output. ### Human-readable receipt Use the smallest report matching the question: ```bash anti-ai today anti-ai week anti-ai month ``` Add `--date YYYY-MM-DD`, `--source codex|claude`, or `--lang zh|en` only when the user requests that scope. Do not run all three reports when one answers the question. The comp