Claude-Mem Agent Cost Report

Acerca de este Skill

Analyze local agent transcripts into an HTML cost report, JSON, CSV line items, and evidence with explicit estimate labels.

Por qué lo elegimos

A reusable workflow from the Claude-Mem project. It is listed separately to explain this task; shared runtime and helper dependencies remain part of the upstream installation. The inherited gallery demonstrates the memory system, not this task’s specific output.

Para qué sirve

• Understand a session or period’s token usage and review work categories and possible rework.

How the workflow runs

1. Step 1

   Choose a project, session, or date range; the default is seven complete Pacific-time days excluding today.

2. Step 2

   Measure transcript tokens, apply saved list-price evidence, and distinguish measured, estimated, and unavailable spending.

3. Step 3

   Review draft work labels against evidence and render the report plus machine-readable files.

Original agent-cost-report instructions

Expected result

HTML report, report.json, line-items.csv, evidence.json; PDF depends on the documented rendering path.

Original agent-cost-report instructions

Try a concrete request

1. Example request

   After installing the required integration, ask your agent:

   Prepare last week’s agent usage report and clearly label list-price estimates versus measured provider charges.

Antes de usarlo

• Bundled Python scripts, Python 3.9+ with timezone data, local Claude Code or Codex transcripts, and network access for list prices. Memory review needs Claude-Mem.
• Use the original upstream files and follow the documented host integration. Model or third-party service usage can carry separate costs.

Agentes compatibles