AB token-tracker
Track and report token usage and cost for conversations. Use when: (1) User asks about token consumption (e.g. "token用了多少", "花了多少钱", "how much did this cost", "usage stats"), (2) At the end of long/complex conversations or tasks to summarize resource usage, (3) User explicitly asks for cost or spending summary. Triggers: token usage, cost tracking, 花费, 用量, 消耗, how much tokens, conversation cost, API cost, spending.
As a process B 67/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, progress reporting
How to improve
- 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: 2. 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 67/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 6 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 394 tokens
- 100Running it twice. No mutating operations
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)
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 418: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 6 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.