A usage dashboard that shows available limits or balances for several coding-agent subscriptions, including Claude, Codex, and DeepSeek.

Use it to check five-hour and weekly limits, DeepSeek balance, reset times, and which services provide no local usage data.

It puts scattered usage information in one place and labels whether each value is live or based on an older record.

usages — Skill for Claude Code by mhlaghari/stuntman

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add mhlaghari/stuntman --skill usages

Clone the repo

git clone --depth 1 https://github.com/mhlaghari/stuntman

Made for: Claude Code.

Or install stuntman, the plugin that ships this one along with the rest of its 9 skills, 9 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/mhlaghari/stuntman/usages/github.svg)](https://agentmods.dev/skills/mhlaghari/stuntman/usages)

Your own site

<a href="https://agentmods.dev/skills/mhlaghari/stuntman/usages"><img src="https://agentmods.dev/badge/skills/mhlaghari/stuntman/usages/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/mhlaghari/stuntman/usages"><img src="https://agentmods.dev/badge/skills/mhlaghari/stuntman/usages.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 114 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 692 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00114	$0.00692
Opus 5.5	$0.00046	$0.00277
Sonnet 5.5	$0.00023	$0.00138
Haiku 4.5	$0.00011	$0.00069

Measured 2mo ago against content hash 57a057434ca7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

usages scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/usages/SKILL.md · 57 lines

How it starts

The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.

stuntman: usages — one board for every subscription

Run the probe and present the board. Everything it reads is zero-token and zero-cost — no worker is invoked.

Run it

Read host and tool setup.

USAGES="$STUNTMAN_ROOT/bin/usages"
"$USAGES" --json

Present it

Render a small table from the JSON — backend, window(s), % used, reset time, freshness. Keep the reset times in the user's local timezone (the pretty mode "$USAGES" already formats them if you prefer to show its output directly).

Explain freshness honestly:

claude and deepseek are live probes (OAuth usage endpoint / balance API). DeepSeek is metered — its "limit" is the remaining balance, so flag a low balance (< $1) as worth topping up.
codex is read from the last rate_limits snapshot in ~/.codex/sessions/ — as fresh as the last codex run. If five_hour_expired / weekly_expired is true, that window has reset since the snapshot (usage is back to ~0%). If snapshot_age_s is large (> a day), say so and mention that any /delegate codex run refreshes it.
agy and muse genuinely expose nothing locally (Antigravity keeps quota server-side; Muse's event stream has no usage) — show them as n/a with that reason, not as an error.

If claude.blocked is true, point at /relay (spanning the cap is exactly what it's for).

For Codex relay decisions, use bin/codex-window from the same bundle. It reads local quota snapshots without probing Claude credentials or DeepSeek. An elapsed reset is not evidence of current usage; check the host's /status if stale.

Status line

In Claude Code, if the user asks for these numbers in their status line, wire "$USAGES" --statusline into their existing statusline command — it prints a compact worker segment (e.g. CX 23%/5h 4%/wk · DS $0.89), caches for 5 minutes (~/.stuntman/usages-cache.txt), and prints nothing on failure, so it's safe to embed. Claude's own numbers are deliberately absent from it — Claude Code's status line JSON already carries them natively. In Codex, present the board in the conversation; do not write Claude's status line configuration or assume Codex accepts the same command format.

Read the full file on GitHub · 57 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago Changed · +8 lines 57a057434ca7
2mo ago First seen · 49 lines · 114 tokens per session scan A 39ac60c281b8

Subscribe to this mod's changes

usages is a skill published in the GitHub repository mhlaghari/stuntman (16 stars, last pushed 20d ago), licensed MIT. It adds 114 tokens to every session and 692 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Analytics and metrics Claude Code Cost Optimization ai-agents claude deepseek llm-orchestration

usages next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
usagesmhlaghari/stuntman	Skill	16	20d ago	MIT	A	114	Claude Code
clawrouterBlockRunAI/ClawRouter	Skill	6.7k	today	MIT	A	171	Claude Code, Codex
imagegenBlockRunAI/ClawRouter	Skill	6.7k	today	MIT	A	45	Claude Code, Codex
phoneBlockRunAI/ClawRouter	Skill	6.7k	today	MIT	A	72	Claude Code, Codex
polymarket-tradingBlockRunAI/ClawRouter	Skill	6.7k	today	MIT	A	76	Claude Code, Codex
releaseBlockRunAI/ClawRouter	Skill	6.7k	today	MIT	A	44	Claude Code, Codex
predexonBlockRunAI/ClawRouter	Skill	6.7k	today	MIT	A	84	Claude Code, Codex