01-usage
/01-usage
Answer what a period or one piece of work consumed in tokens, per day, model, agent, tool, task, ticket, session, repository or person, from the local measurement. Use when the user asks how many tokens were spent, where the effort went, or what a task or ticket consumed. Not for turning measurement on or off.
- Author
- ai-driven-dev ↗
- Repository
- framework ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Answer what a period or one piece of work consumed in tokens, per day, model, agent, tool, task, ticket, session, repository or person, from the local measurement. Use when the user asks how many tokens were spent, where the effort went, or what a task or ticket consumed. Not for turning measurement on or off.
Arguments
/01-usage question | period
Original author description
Answer what a period or one piece of work consumed in tokens, per day, model, agent, tool, task, ticket, session, repository or person, from the local measurement. Use when the user asks how many tokens were spent, where the effort went, or what a task or ticket consumed. Not for turning measurement on or off.
How it works
- Actions
- Transversal rules
SKILL.md preview
---
name: 01-usage
description: Answer what a period or one piece of work consumed in tokens, per day, model, agent, tool, task, ticket, session, repository or person, from the local measurement. Use when the user asks how many tokens were spent, where the effort went, or what a task or ticket consumed. Not for turning measurement on or off.
argument-hint: question | period
---
# Usage
```mermaid
flowchart TD
question([question]) --> probe{"aidd answers telemetry?"}
probe -->|"no"| absent([say it is missing, answer nothing])
probe -->|"yes"| frame
frame -->|"no axis fits"| refuse([say what the report cannot split by])
frame --> answer
answer -->|"refused or unknown version"| stop([say so])
answer --> told([figures, with what is unknown])
```
## Actions
Run the flow above. Read only the next action file.
| Action | Does |
| --- | --- |
| frame | map the question to a period, one axis and the filters it fixes, and name the command |
| answer | run it, read the JSON, and state the figures with what is unknown |
## Transversal rules
- Probe first. Run `aidd telemetry --help` before any action. When `aidd` is not found, or the command exits non-zero, stop and say plainly that `aidd` is missing or too old to report, name `@ai-driven-dev/cli` as what to install or update, and state that no figure is available. Never answer from memory, from the session, or from anything but the report.
- Every figure comes from `aidd telemetry report --json`. Never add, subtract, average, convert or estimate a number, and never turn tokens into money: the report holds counts only.
- Keep input, output, cache read and cache write apart. A total is the report's own `total`, not a sum made here.
- An unknown is unknown, never zero. Say so whenever the report shows one.
- Read only. Nothing here declares a task, turns measurement on, or changes any file.
Files in this package (4)
- SKILL.md 2 KB
- actions/answer.md 3 KB
- actions/frame.md 4 KB
- references/envelope.md 6 KB
Versions
The database has no other skills named 01-usage.
Database snapshot: 13.11.2026 · package version a39b6739106f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100cost-tracking
Track and report OpenAI Codex token usage, spending, and budgets from a local cost-tracking database. Use when the user asks about costs, spending, usage, tokens, budgets, or cost breakdowns by project, tool, session, or date. - 100claude-token-audit
Show where Claude Code tokens and usage limits go, from the local session logs in ~/.claude/projects. Breaks usage down by project, session, day, model and tool, finds the biggest tool outputs flooding the context, measures cache hit rate and peak context per session, sizes what… - 100token-audit
Use when the user asks where their Claude Code usage/tokens are going, is burning through their plan unexpectedly fast, hitting limits, or wants a breakdown of Claude Code activity. Produces a COMPREHENSIVE usage report from local session transcripts: tokens by… - 100cost-tracking
Track and report Claude Code token usage, spending, and budgets from the local ECC cost-tracker metrics log. Use when the user asks about costs, spending, usage, tokens, budgets, or cost breakdowns by model, session, or date. - 100usage-reporter
Report the token usage of a build to PAPI from your AI client's own local transcript. Optional. Use when completing a build and you want tokens recorded, or when asked what a task or stage cost in tokens. Reads only numeric usage, never prompts or responses. - 90choose-effort
Asks the user how much effort a Claude Code task deserves before heavy work starts, then recommends an effort level, whether to fan out to subagents, goal mode, workflows or agent teams, how to set it, and when to check /usage. Use when the user is about to start a large, long…