Tracking Codex Astra costs took more than updating a price table

Description and use

The agent‑cost CLI now correctly calculates Codex GPT‑6 Astra usage, applying Fast mode multipliers and marking ambiguous usage as unpriced, providing transparent cost estimates.

Problem

The agent-cost CLI could not correctly price Codex GPT‑6 Astra usage, treating Fast mode as Standard and leaving some usage unpriced.

Outcome

Fast‑mode usage is now priced correctly; ambiguous settings remain unpriced with tokens preserved, providing transparent cost estimates.

Workflow

• 1. Update agent‑cost to v0.1.1 and add Astra rates to price catalog.
• 2. Run synthetic tests with 2M cached, 2M uncached, 2M output tokens.
• 3. Identify log settings (Standard, Fast, Unknown).
• 4. Detect service_tier and model name; apply multiplier only when mode is clear.
• 5. Mark ambiguous or missing settings as unpriced and record unpriced_tokens.
• 6. Generate report with pricing_status, estimated USD, credits, and unpriced token count.
• 7. Verify output via uvx commands (doctor, report).

Evidence

After adding Astra to the price table, I tested it with synthetic logs. Usage marked as Fast was still being priced at the Standard rate.

Source

The fix involved both detecting the mode and deciding what to do when the logs didn’t give me enough information.

Source

Instead, usage stays unpriced when the reader can’t determine which rate applies.

Source