AC model-usage
Use CodexBar CLI local cost usage to summarize per-model usage for Codex or Claude, including the current (most recent) model or a full model breakdown. Trigger when asked for model-level usage/cost data from codexbar, or when you need a scriptable per-model summary from codexbar cost JSON.
As a process C 64/100 · Has gaps — weak spots: failures and branches, consistency, 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
exfil-webhook-urldocs/ALERT_CONFIG_EXAMPLE.json:9Webhook / callback URL commonly used for exfiltration (verify the destination) (test fixture / example file; quoted — discussed, not commanded)"slack:webhook:https://hooks.slack.com/services/xxx/yyy/zzz",
fixturequoted -
low Exfiltration
exfil-webhook-urldocs/ALERT_CONFIG_EXAMPLE.json:10Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)"discord:webhook:https://discord.com/api/webhooks/..."
placeholder
Files scanned: 14. 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 64/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (model-usage) differs from the folder (token-usage-dashboard)
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 11 steps
- 100Execution cost. Instruction body is 430 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- -5TODO / placeholder text left in the skill
- -32 of 4 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 291: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 11 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (1 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.