# 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.

- Skill: `ai-driven-dev/01-usage` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx get-skill add ai-driven-dev/01-usage`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ai-driven-dev/01-usage/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: ai-driven-dev (https://skillmd.com/u/ai-driven-dev)
- Updated: 2026-11-11
- Page: https://skillmd.com/skills/ai-driven-dev/01-usage

---


# 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.

