Stack measure
Measure token usage and savings via ccusage — establish a baseline and compare before/after. Use right after init (to record the baseline) and again after about a week to quantify the input-token reduction against the ≥40% target. Wraps `agent-stack measure`, which reads ccusage's local JSONL — never vendor self-reported numbers.From its SKILL.md
npx -y skills add drmahdikazempour/agent-stack --skill stack-measureAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
- runs commandsInstructs the agent to run 3 commands, including `npx @drmahdikazempour/agent-stack measure` and 2 more.
SKILL.md
1.1 KB, 185 tokens by cl100k_base, as published. Nobody here has run it
stack-measure
Quantify token usage with the neutral ccusage tool. Savings are always measured, never claimed.
What to do
- Baseline:
npx @drmahdikazempour/agent-stack measure(init already stored one in.agent-stack/baseline.json). - Compare:
npx @drmahdikazempour/agent-stack measure --since 7d— reports baseline vs recent average input tokens/day and the % reduction, color-coded against the ≥40% target.
Notes
- If
ccusageisn't installed, the command falls back to the localusage.jsonlourStophook appends; installccusage(npm i -g ccusage) for authoritative numbers. - Telemetry-free and local-only: it reads ccusage's JSONL on the user's machine.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.