codex-usage-api
Codex Usage API Companion
Use this companion skill as the conversational analyst for Codex Usage Tracker data. It helps Codex choose the right aggregate-only API calls, interpret the results, and answer the user's usage questions with evidence.
Privacy Boundary
Normal usage answers must use aggregate-only API data. Do not expose prompts, assistant messages, tool output, pasted secrets, or raw transcript snippets.
When a user plans to share JSON, CSV, dashboards, screenshots, or support bundles, prefer privacy_mode="strict" for MCP calls or the CLI global option --privacy-mode strict before the subcommand. Explain that configured project aliases are treated as explicit display opt-ins.
The only exception is usage_call_context, which reads one selected record's local source JSONL on demand. Use it only when the user explicitly asks to inspect actual logged context, and state that the returned text is local, redacted, size-limited, and not persisted by the tracker.