claude-usage-analyst

claude-usage-analyst is a skill for Claude Code, Codex from daymade/claude-code-skills. It costs 91 tokens per session (629 once invoked), scanned A, original, MIT.

An analyst for Claude Code and Claude Desktop usage records, using ccusage data to examine tokens, costs, model use, cache activity, and five-hour quota periods.

In plain words
What is it for?
Investigating daily or historical usage, comparing models, analysing cost and token patterns, and explaining quota consumption.
Why use it?
It separates measured usage from interpretation, helping explain why a quota was exhausted or why one model used more resources.

Skill for Claude CodeCodex

Written for Claude Code and Codex: disable-model-invocation in frontmatter, but also agents/openai.yaml present. Also seen: mentions Claude Code.

Part of the daymade-claude-code plugin — 21 skills shipped together

Good fit Investigating daily or historical usage, comparing models, analysing cost and token patterns, and explaining quota consumption.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/daymade/claude-code-skills/claude-usage-analyst
About the project

Claude Code Skills Marketplace is a collection and marketplace of skills, plugins, agents, and instructions that extend Claude Code with specialized development workflows. It is for developers who want to install existing workflows or create, validate, and package their own Claude Code skills.

daymade/claude-code-skills · 1,516 stars · on GitHub

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 daymade/claude-code-skills --skill claude-usage-analyst
Clone the repo
git clone --depth 1 https://github.com/daymade/claude-code-skills

Made for: Claude Code, Codex.

Or install daymade-claude-code, the plugin that ships this one along with the rest of its 21 skills.

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.

agentmods badge for claude-usage-analyst

README.md
[![agentmods](https://agentmods.dev/badge/skills/daymade/claude-code-skills/claude-usage-analyst/github.svg)](https://agentmods.dev/skills/daymade/claude-code-skills/claude-usage-analyst)
Your own site
<a href="https://agentmods.dev/skills/daymade/claude-code-skills/claude-usage-analyst"><img src="https://agentmods.dev/badge/skills/daymade/claude-code-skills/claude-usage-analyst/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.

agentmods 80×15 button for claude-usage-analyst

Your own site · 80×15
<a href="https://agentmods.dev/skills/daymade/claude-code-skills/claude-usage-analyst"><img src="https://agentmods.dev/badge/skills/daymade/claude-code-skills/claude-usage-analyst.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 91 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 629 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 warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium MCP Rug Pull · line 18
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00091 $0.00629
Opus 5.5 $0.00036 $0.00252
Sonnet 5.5 $0.00018 $0.00126
Haiku 4.5 $0.00009 $0.00063

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

Security

Grade A, and why

claude-usage-analyst 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 1mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/analyze_claude_usage.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

daymade-claude-code/claude-usage-analyst/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.

Claude Usage Analyst

Overview

Use this skill to produce evidence-based usage explanations from local ccusage data. Separate observed numbers from interpretation, and explain quota burn in human terms.

Workflow

  1. Verify ccusage is available:

    ccusage --version
    

    If missing, install or update with npm install -g ccusage@latest or run with npx ccusage@latest.

  2. Run the bundled analyzer for the requested window:

    python3 /path/to/claude-usage-analyst/scripts/analyze_claude_usage.py \
      --since YYYY-MM-DD --until YYYY-MM-DD --timezone Asia/Shanghai
    

    Default --since/--until is today in the selected timezone. For historical comparison, set --since to an earlier date such as the first day of the month; otherwise rank/median fields only describe the single target day.

  3. If the user asks about a specific model comparison, pass aliases:

    python3 scripts/analyze_claude_usage.py --model-a fable --model-b opus-4-8
    
  4. Read references/explanation-guide.md when writing the final answer.

Evidence Rules

  • Base numeric claims on ccusage output or the bundled analyzer output.
  • State the scope: ccusage claude measures local Claude Code usage logs, including Claude Desktop's Claude Code sessions when those local logs exist. It is not a complete ordinary Claude.ai chat bill.
  • Report dates with timezone.
  • Explain cache clearly: cache read tokens are still usage/quota pressure even though the user did not type those words.
  • Do not infer Anthropic plan quota rules from local token counts unless the user provides plan details. Say "quota-like pressure" or "ccusage estimated cost/token burn" when exact plan accounting is unknown.
  • When comparing models, compare both token volume and estimated cost. A model can have similar token volume but higher cost.

Output Shape

Use this structure unless the user asks otherwise:

  1. Short conclusion in plain language.
  2. Evidence table: total tokens, cost, input, output, cache create, cache read.
  3. Model comparison table.
  4. 5-hour block table when quota exhaustion is discussed.
  5. Explanation of why the burn happened.
  6. Confidence and caveats.

Read the full file on GitHub · 57 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

  1. 1mo ago Changed · +1 lines 4c6bb36cb59c
  2. 2mo ago First seen · 56 lines · 91 tokens per session scan A 2937e96ac368

Subscribe to this mod's changes

claude-usage-analyst is a skill published in the GitHub repository daymade/claude-code-skills (1,516 stars, last pushed yesterday), licensed MIT. It adds 91 tokens to every session and 629 once invoked, about $0.0004 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.

Related

claude-usage-analyst compared with skills from other repositories

claude-usage-analyst next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
claude-usage-analystdaymade/claude-code-skillsSkill1.5kyesterdayMITA91Claude Code, Codex
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code