AD token-stats-skill
Record and analyze token usage from Codex, Claude Code, OpenClaw, Hermes Agent, OpenCode, DeepSeek Harness, WorkBuddy, WorkBuddy AI, and cached Trae CN account usage with token-stats v0.0.4. Use for source diagnostics, daily records, date-range analysis, optional Trae CN synchronization, or user-approved periodic offline collection. Local logs and account-wide Trae data have different scopes; neither is a billing invoice.
Record and analyze token usage from Codex, Claude Code, OpenClaw, Hermes Agent, OpenCode, DeepSeek Harness, WorkBuddy, WorkBuddy AI, and cached Trae CN…
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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: 10. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary"
Process rating: all ten parameters 43/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 100Steps. 22 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1826 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 425: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 22 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 3 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.