SKILLEMALL.ai

AB ccusage-report

Report Claude Code token consumption and costs using ccusage. Use when the user asks about their Claude Code usage, token consumption, API costs, spending, or wants a daily/weekly/monthly usage summary. Triggers on: "show my claude code usage", "how much did I spend", "my token consumption", "ccusage report", "usage report", "token consumption", "how much did I spend".

modbender/skill-library-mcp Agent Skills author: modbender MIT 3 files body ≈ 491 tokens Open the sourcegithub.com analyzed 3 d ago

Report Claude Code token consumption and costs using ccusage.

As a process B 68/100 · Nearly there — weak spots: result and completion, inputs and preconditions, progress reporting

ProcedureData and analyticsSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
89
Run on models
none yet
Process rating
B
68/100
Nearly there
Result and completion w 14
0
Progress reporting w 2
0
Inputs and preconditions w 11
30
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 68/100

    • 0Result and completion. Does not say what the result is
    • 0Progress reporting. Says nothing while it works
    • 30Inputs and preconditions. Does not say what the process needs to start
    • 55Failures and branches. 1 branches
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. No external tools needed
    • 100Steps. 8 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 491 tokens
    • 100Running it twice. Mutating operations check current state

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 7 example trigger phrases
    • +3Description length 371: enough signal without eating the budget
    • +4Structure: 8 headings
    • +3Step-by-step instructions: 8 items
    • +4Has examples (2 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.