ModsCode / Claude Code Mods / Ranking / usage-radar
usage-radar
Shows how much of your Claude plan limits you have used, when they reset, and whether your current pace may reach them first.
What it does
- Draws a band above the prompt, a pane
- Hooks session.measure, session.start
- Keeps its own state between turns
Good points
- No network calls
- Starts no processes
- Written in TypeScript
- Handles errors
Code to start from
A starter ModsCode writes from the drawing it read, and the mod's own lines that draw, where there are any.
Starter (register.tsx)
import type { Register } from 'claude-code'
// Drawn like usage-radar by JJ Englert (pane, band, status, toast), as ModsCode read it from the mod's code:
// https://modscode.com/claude-mods/mods/jjenglert1-usage-radar/
// Written by ModsCode from that reading, not copied from the mod: use it as you like.
// Each value below stands for one the mod works out at run time; put in your own.
export const register: Register = on => {
// the band above the prompt; what else goes there is drawn under it
on('ui.render', { component: 'AbovePrompt' }, async ($, e, next) => {
const { Box, Text, Button } = $.ui.resolve(e)
const text = '…'
return (
<Box flexDirection="column">
<Box flexWrap="wrap">
<Text>
{text}
{" "}
</Text>
<Button label="Details" />
<Button label="Hide" />
</Box>
{await next(e)}
</Box>
)
})
// the pane: open it with $.ui.open({ id: 'my-pane', title: "Usage Radar" })
on('ui.render', { component: 'Pane', requestId: 'my-pane' }, async ($, e) => {
const { Box, Text, Button } = $.ui.resolve(e)
const windowTitle = '…'
const formatPercent = '…'
const formatRate = '…'
const forecastLong = '…'
const basisLine = '…'
const windowTitle2 = '…'
const formatPercent2 = '…'
const formatRate2 = '…'
const forecastLong2 = '…'
const basisLine2 = '…'
const windowTitle3 = '…'
const formatPercent3 = '…'
const formatRate3 = '…'
const forecastLong3 = '…'
const basisLine3 = '…'
const levelsText = '…'
const MIN_SPAN_MIN = '…'
return (
<Box flexDirection="column">
<Box flexDirection="column" marginBottom={1}>
<Text bold>
Reading unavailable
</Text>
<Text dimColor>
No plan limits came back, or the read failed. API-key accounts have none. Usage Radar keeps trying once a minute.
</Text>
</Box>
<Box flexDirection="column" marginBottom={1}>
<Text bold>
{windowTitle}
{": "}
{formatPercent}
</Text>
<Text>
████████░░░░░░░░
</Text>
<Text>
Resets:
{" "}
not reported
</Text>
<Text>
Burn rate:
{" "}
{formatRate}
</Text>
<Text>
{"Forecast: "}
{forecastLong}
</Text>
<Text dimColor>
{"History: "}
not enough readings yet
</Text>
<Text dimColor>
{basisLine}
</Text>
</Box>
<Box flexDirection="column" marginBottom={1}>
<Text bold>
{windowTitle2}
{": "}
{formatPercent2}
</Text>
<Text>
████████░░░░░░░░
</Text>
<Text>
Resets:
{" "}
not reported
</Text>
<Text>
Burn rate:
{" "}
{formatRate2}
</Text>
<Text>
{"Forecast: "}
{forecastLong2}
</Text>
<Text dimColor>
{"History: "}
not enough readings yet
</Text>
<Text dimColor>
{basisLine2}
</Text>
</Box>
<Box flexDirection="column" marginBottom={1}>
<Text bold>
{windowTitle3}
{": "}
{formatPercent3}
</Text>
<Text>
████████░░░░░░░░
</Text>
<Text>
Resets:
{" "}
not reported
</Text>
<Text>
Burn rate:
{" "}
{formatRate3}
</Text>
<Text>
{"Forecast: "}
{forecastLong3}
</Text>
<Text dimColor>
{"History: "}
not enough readings yet
</Text>
<Text dimColor>
{basisLine3}
</Text>
</Box>
<Text>
Last updated: no reading yet
</Text>
<Text>
{"Warning levels: "}
{levelsText}
{" (change: /usage-radar warn 70 90)"}
</Text>
<Box flexDirection="column" marginTop={1}>
<Text bold>
How the forecast works
</Text>
<Text dimColor>
It takes a reading of your plan limits once a minute and whenever the figures move. For each window it looks only at th…
</Text>
<Text dimColor>
{"It needs at least "}
4
{" readings over "}
{MIN_SPAN_MIN}
+ minutes first. If the rate would take you to 100% before the reset time, it says you may reach the limit.
</Text>
<Text dimColor>
It is an estimate from your recent pace, not a promise. It cannot tell whether a particular task will fit in what is le…
</Text>
</Box>
<Box marginTop={1}>
<Button label="Show strip" />
</Box>
</Box>
)
})
}
The mod's own code
Its licence text was not found at the commit read, so only the places in the source are linked.
plugins/usage-radar/hooks/register.tsxlines 219–244plugins/usage-radar/hooks/register.tsxlines 246–323
How to build this: Pane (panel), Keep state with $.store
What its code calls
remembers
What its code shows
Read from the source at commit 8b638814dd3f on 2026-10-11. The first group decides whether a mod is listed; the rest is for you to weigh. A later commit is not read until the next crawl.
| Decides the listing: code you can check | |
|---|---|
| Entry read | Every module hooks/hooks.json names was read.plugins/usage-radar/hooks/register.tsx |
| Parses | Every file parses as TypeScript or JavaScript.2 files parsed |
| All its code is in the mod | Every import is a file of the mod or the engine's own module; no packages, no require.all its code is in the mod |
| Readable | No minified lines, no eval or new Function, no import of a computed path, no encoded blobs.no minified code, no eval, no encoded blobs |
| Calls in the open | Network and programs are reached as $.http.fetch and $.process.run in place, never passed around.every call outside goes through $ in the open |
| For you to weigh before installing | |
| Where it draws | The terminal, the desktop app, both, or nothing (hooks only: a guard or a prompt rewriter), as its code says. Shown, never a reason to leave a mod out.draws in the terminal and the desktop app, the same in both |
| Install line | Whether its repository's own .claude-plugin/marketplace.json lists it, so it installs from that marketplace with the lines on its page.listed in its repository's .claude-plugin/marketplace.json: installs from there |
| Programs on Windows | Whether every program it starts through $.process exists on Windows (tail, date, open, osascript, /usr/… do not).runs no program a Windows PC lacks |
| Network | Whether every fetch names its https host in the code.no network |
| Programs | Whether every program it starts is named in the code and is not a shell, an interpreter or a network tool.starts no programs |
| Reads and sends | Whether it both reads something of yours (files, environment variables, the transcript, settings) and reaches outside (the network, an MCP server, another session, telemetry).reaches nothing outside |
| Keys in the source | Whether the source holds what looks like an API key or a private key.no keys in the source |
| Licence | An open licence (MIT, Apache-2.0, BSD, ISC, Unlicense, 0BSD, CC0) with its text lets ModsCode show its code; otherwise the code is linked.no licence |
| Settings hooks | Hooks declared in hooks/hooks.json or plugin.json beside the module: a command (a shell when it has no args), an HTTP request, an MCP tool or a model prompt at an event. They run outside $.no settings hooks: its function hooks alone |
| Servers it ships | MCP servers (a program, or a URL; a headersHelper is a shell command; a .mcpb bundle is unpacked at run time), LSP servers, monitors (a shell command for the whole session) and bin/ (on the PATH of the Bash tool).ships no MCP or LSP server, no monitor, no bin/ |
| Skills, commands, agents | What its Markdown declares beyond text: allowed-tools granted for the turn, hooks added when a skill is invoked, a command run before Claude reads the skill.no skills, commands, agents or workflows |
| Tools and MCP | Whether every tool it calls through $.tool.call and $.mcp.call is named in the code, and none is a shell (Bash through the tool runs a shell without $.process).calls no tool, MCP server or command |
| Asks of the model | Completions it runs ($.model.complete, fork, classify), subagents it spawns, prompts it submits as you, and the tools, commands and agents it adds.adds command ? |
| Events it hooks | By what a hook there can do: gates (refuse a tool call, a prompt, a setting, another plugin), shapes (what the model reads: the system prompt, tool descriptions, each request), reads (your input, the events of the settings hooks, every event with *), and the rest.gates: command.run · also: session.start, session.measure, ui.render (AbovePrompt, Pane) · timers: clock.every |
| Reads, by name | The environment variables and files it names, and whether it reads the transcript, settings.json, the prompt box or the mouse selection.reads no files, environment variables, settings or transcript |
| Writes, by name | The files and environment variables it names, and whether it changes settings, the prompt box, the clipboard, the conversation (a row the model reads) or another session.writes no files, environment variables, settings or conversation rows |
This is a reading of the code text, not a security review: it does not run the mod, and it cannot see what a program the mod starts does. The check before installing is yours. How mods are chosen
Install it
Check it yourself before you install it. Mods run unsandboxed, with your permissions, and ModsCode does not vouch for what this code does. Read its code (or run claude plugin validate . in its folder), weigh what it reaches, and install the commit you read.
From its marketplace
Its repository is its marketplace. Add that marketplace (in the terminal with these commands, or in the desktop app's plugin settings) and install the mod from it:
/plugin marketplace add JJenglert1/claude-mods/plugin install usage-radar@claude-mods/reload-pluginsThis installs the marketplace's latest commit, which may not be the one read here (8b638814dd3f). Compare them before you install. /reload-plugins loads it into a session that is already open.
Try the commit ModsCode read
No marketplace needed. In a terminal, clone the repository, check out the commit read, validate the mod, and load it for one session:
git clone https://github.com/JJenglert1/claude-modsgit -C claude-mods checkout 8b638814dd3f85d99d2c36a526eb4ab4f261a03bclaude plugin validate claude-mods/plugins/usage-radarclaude --plugin-dir claude-mods/plugins/usage-radarThe validate line lists the events the mod hooks and what it asks Claude Code to do, without running it. The last line loads the mod for this session only and writes nothing to your settings. If the author has rewritten history, the commit may no longer exist.
Ask Claude about it
With the ModsCode connector added, Claude can read this mod's code and what it reaches, and build on them. Ask it like this:
Read the ModsCode mod "jjenglert1-usage-radar" with its code and make me one like itSearch them from Claude: the MCP connector
Similar mods
- code-modernizationAnthropic★ 37,653
- crit-tuiTomasz Tomczyk★ 1,196
- remctlFederico Viticci★ 595
- task-orchestrator-modJeff Picklyk★ 208
- localvoxtral-modlocalvoxtral★ 59
- localvoxtral-remotelocalvoxtral★ 59
More from this repository
- agentpaneJJ Englert★ 0
- blast-radiusJJ Englert★ 0
- quest-modeJJ Englert★ 0
- replay-theaterJJ Englert★ 0
- screen-cloakJJ Englert★ 0
- spaceship-bridgeJJ Englert★ 0
See all 8 mods in this repository
Badge for your README
If this is your mod, paste this into your README. It links to this page.
[](https://modscode.com/claude-mods/mods/jjenglert1-usage-radar/)