Credentials. Session logs can contain prompts, code and file content, so review the output before you share anything outside your machine.
Who it is forA developer or team lead who runs Codex or Claude Code daily and suspects that retries or duplicate records are inflating token usage.
The problemSession logs show more usage than expected, and it is unclear whether the extra counts come from duplicate records, retries or real work.
The outcomeA local report that flags duplicate records, retry amplification and token anomalies, with the note that missing evidence stays unknown and a retry is not automatically a second operation.
What you need first
- Python 3.9 or newer and pip
- A terminal on macOS, Linux or Windows
- A vendor billing export as CSV for the recount use case, or local Codex or Claude Code session logs for the log use cases
- Permission to read the session logs or export files you point the tool at
Steps
- Run
pip install agentmeasureto install the CLI. - Run
agentmeasure demoto see the output on a bundled synthetic session with no account and no upload. - Run
agentmeasure checkto inspect your default seven-day window of local sessions. - If the check finds no logs, run
agentmeasure check --allor pass an explicit--dirand--runtime. For Claude Code, runagentmeasure check --runtime claude. (inferred, check the README) - Review each flagged item and treat a missing input as a gap, not a pass.
Prompt for your agent
Using the AgentMeasure repo, run `agentmeasure check --runtime claude` on this machine and report duplicate records, retry amplification and token anomalies, with any missing inputs listed separately. Verify that the report states which inputs were not found instead of marking them as passing.
Caveat. With both runtimes present, auto-discovery prefers Codex, so pass `--runtime claude` explicitly when you mean Claude Code.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page