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.
npx agentmods add skills/eltonylfgi-blip/claude-code-usage-guard/usagenpx skills add eltonylfgi-blip/claude-code-usage-guard --skill usagegit clone --depth 1 https://github.com/eltonylfgi-blip/claude-code-usage-guardWrote 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.
[](https://agentmods.dev/skills/eltonylfgi-blip/claude-code-usage-guard/usage)<a href="https://agentmods.dev/skills/eltonylfgi-blip/claude-code-usage-guard/usage"><img src="https://agentmods.dev/badge/skills/eltonylfgi-blip/claude-code-usage-guard/usage.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00074 | $0.00712 |
| Opus 5 | $0.00037 | $0.00356 |
| Sonnet 5 | $0.00015 | $0.00142 |
| Haiku 4.5 | $0.00007 | $0.00071 |
Grade B, and why
usage scanned grade B with 1 finding 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 5d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
large files). Keep it to one line — do not lecture. How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Usage status
Report the user's current Claude Code usage by reading the locally-captured plan quota and their local session transcripts.
Steps
-
Run the engine:
node "${CLAUDE_PLUGIN_ROOT}/lib/engine.mjs"- If the status-line shim has been wired up (see README §3.5), the output LEADS with a
"Real plan quota" block: the actual 5-hour and weekly
used_percentageand reset times. This is the number that truly gates the user — report it first. - Below that it prints the weighted-spend proxy for the last 5 hours: burn rate, output/input/cache tokens, turn count, and models used.
- If the status-line shim has been wired up (see README §3.5), the output LEADS with a
"Real plan quota" block: the actual 5-hour and weekly
-
If the "Real plan quota" block is present, report those percentages and reset countdowns as the headline. If it is ABSENT, tell the user real quota isn't being captured yet and that they can enable it by wiring the status line (README §3.5) — until then, fall back to the proxy.
-
If a config file exists at
~/.claude/usage-guard.jsonwith aweightBudget, also compare the weighted spend against it (e.g. "72% of your 8M fallback budget"). If no budget is set and no real quota is captured, say so and point to the two ways to enable warnings. -
Present a short, plain-language summary (define any jargon in-line). Example shape:
- Plan quota: 5h 88% used (resets in 1h 29m) · weekly 41% — when available
- Spent (last 5h, proxy): 4.5M weighted · burn rate ~1.2M/h
- Breakdown: output 183k · fresh input 417k · cache 3.1M created / 8.4M read
-
If usage is high or the burn rate is climbing, give ONE concrete tip to slow the spend (e.g. start a fresh session to drop the cache-read tail, batch questions, avoid re-reading large files). Keep it to one line — do not lecture.
Notes
- Real plan quota comes from Claude Code's
rate_limits(5h + weekly), captured by the status-line shim to~/.claude/.usage-guard-limits.json. It's the actual plan limit, not a guess. Present only for Claude.ai Pro/Max after the first API response. - "Weighted spend" is the FALLBACK proxy: input + output + cache-creation at face value,
cache-read counted at 0.1 (it is ~10x cheaper). A proxy, not an exact bill and not the plan
quota — used when real
rate_limitsaren't available. - The engine has zero dependencies and only reads local files; it never makes network calls.
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.
- 5d ago First seen · 51 lines · 74 tokens per session scan B dbb284f6ce2c
usage is a skill published in the GitHub repository eltonylfgi-blip/claude-code-usage-guard (3 stars, last pushed 5d ago), licensed MIT. It adds 74 tokens to every session and 712 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
better-auth
Skill for integrating Better Auth - comprehensive TypeScript authentication framework for Cloudflare D1, Next.js, Nuxt, and 15+ frameworks. Use when adding auth, encountering D1 adapter errors, or implementing OAuth/2FA/RBAC features.
cloudflare-cron-triggers
Cloudflare Cron Triggers for scheduled Workers execution. Use for periodic tasks, scheduled jobs, or encountering handler not found, invalid cron expression, timezone errors.
aceternity-ui
100+ animated React components (Aceternity UI) for Next.js with Tailwind. Use for hero sections, parallax, 3D effects, or encountering animation, shadcn CLI integration errors.
cloudflare-durable-objects
Cloudflare Durable Objects for stateful coordination and real-time apps. Use for chat, multiplayer games, WebSocket hibernation, or encountering class export, migration, alarm errors.
cloudflare-sandbox
Cloudflare Sandboxes SDK for secure code execution in Linux containers at edge. Use for untrusted code, Python/Node.js scripts, AI code interpreters, git operations.
cloudflare-workflows
Cloudflare Workflows for durable long-running execution. Use for multi-step workflows, retries, state persistence, or encountering NonRetryableError, execution failed errors.