RSS
Tools

Six weeks after launch, about 2,300 GitHub repos call themselves a Claude Code mod

Six weeks after Claude Code mods launched, about 2,300 GitHub repositories describe themselves as a Claude Code mod, and hundreds of them mention usage. The usage meters read your limits in three different ways.

Close-up of a round meter illustrating the count of GitHub repos calling themselves Claude Code mods
Photo by Liam Briese on Unsplash

Claude Code mods launched on October 1 with version 2.1.287. By November 14, a GitHub search found 2,308 repositories whose description contains the phrase "Claude Code mod". Of the repositories with that phrase in their name or description, 346 also mention usage and 20 mention a theme.

Treat those as keyword counts, not a census. They don't show how many repositories hold a working, maintained mod, and they miss mods that describe themselves differently. Most of the usage-meter repositories we opened had no stars at all; the most-starred one in our sample had 32.

Why usage meters show up so often

Plan users have a 5-hour and a weekly limit, and the /usage command shows where they stand. A mod can keep those figures on screen, in a band above the prompt or a line in the footer, so it is an obvious first project. The interesting difference between the meters is where their numbers come from.

Three ways to read your limits

  • The mods API. $.session.usage() returns the session's context and cost, plus a list of the account's rate limits, each with the share used and the reset time. The limit readings come from the session's last API response. aliahmadcse/claude-usage-status reads it on a one-minute timer. The author of another meter notes that mods relying on these figures can stay blank until Claude first answers.
  • Anthropic's usage service. anantraghunath/claude-code-usage-quota-mod asks api.anthropic.com/api/oauth/usage about every 2 minutes, and zoyluoblue/claude-usage about every 5 minutes, both through Claude Code's own signed-in connection. The usage-quota README says Claude Code attaches the credential without the mod seeing it, and that the request uses no tokens.
  • A background /usage. ramzigz/claude-usage-bar runs claude -p /usage --no-session-persistence every 2 minutes. Its README says that uses no tokens and that the figures include your other sessions and claude.ai.

All three can show the account-wide plan limits. The practical difference is freshness: the mods API reports what the last reply carried, so an idle or newly opened session may show old or no numbers, while the other two fetch readings at startup and while you are away.

Try it with your AI. Or skip the strangers' code and have Claude Code write a meter that uses only the official mods API. Paste this into a Claude Code session:

Make a Claude Code mod that shows my 5-hour and weekly plan usage in a band above the
prompt.

- Read the limits only with $.session.usage(): use rateLimits (percentUsed and resetsAt)
  and the context percentage.
- Refresh on a one-minute timer and after each turn. Show each limit as a short bar with
  its percentage and the time until it resets.
- Make no network requests of your own, start no processes, and don't read any
  credential or settings files.
- If no reading is available yet, show "waiting for first reply" instead of an empty
  bar.

When it works, tell me how to copy it out of this session's dev-mods folder and load it
in other sessions with --plugin-dir.

Before you install one

A usage meter sounds harmless, but every mod runs with your permissions and can make network requests. The better READMEs list exactly which requests they send. You can check for yourself before installing: clone the repository and run claude plugin validate on it, which lists the events a mod handles and the calls it makes without running it.

Source: GitHub repository search: "Claude Code mod", Claude Code v2.1.287 release notes, Mods reference (Claude Code docs), anantraghunath/claude-code-usage-quota-mod, ramzigz/claude-usage-bar, aliahmadcse/claude-usage-status, zoyluoblue/claude-usage

This story first appeared in the claudefox daily briefing for November 14, 2026.