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.

564 stars 65 forksProductivity & Notes Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add ai-driven-dev/framework

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add ai-driven-dev/framework --skill 01-usage
Manual install
git clone --depth 1 https://github.com/ai-driven-dev/framework.git /tmp/framework
mkdir -p ~/.claude/skills
cp -r /tmp/framework/plugins/aidd-telemetry/skills/01-usage ~/.claude/skills/01-usage

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# 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.
Read the full skill on GitHub

Details

Skill name
01-usage
Path
plugins/aidd-telemetry/skills/01-usage/SKILL.md
License
MIT
Repo updated
18 November 2026

FAQ

What does the 01 Usage skill do?

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 do I install the 01 Usage skill?

Claude Code plugin: /plugin marketplace add ai-driven-dev/framework. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is 01 Usage popular?

It lives in ai-driven-dev/framework, which has 564 GitHub stars and 65 forks.

Related skills

00 Async Dev

564

ai-driven-dev/framework

Drive the async-dev pipeline from one entry point, whether setup, run, or review. Use when the user wants to install async dev, run a ready issue, or address PR review comments, or on a webhook trigger. Not for plain status checks.

Git & Code Review65

00 Init

564

ai-driven-dev/framework

Turn AIDD measurement on for a project after explicit consent, stop it, choose to be named on your own measurement, or delete what was measured. Use when the user wants to start or stop measuring what their work consumes, add or remove their name, or forget measured data. Not for answering what a period consumed.

Other65

00 Onboard

564

ai-driven-dev/framework

Guide a project's journey through AIDD, from first setup to shipping a feature. Use when the user says onboard me, where do I start, or what to do next. Not for listing every installed surface.

Other65

02 Project Memory

564

ai-driven-dev/framework

Set up, refresh or wire the project memory of its architecture, conventions and decisions into your AI tools. Use for any project memory request, even a bare "check". Not for one-file edits.

Productivity & Notes65

01 Brainstorm

564

ai-driven-dev/framework

Clarify a vague idea through questions. Use when the user has a half-formed idea, ambiguous request, or asks to brainstorm, discover, refine, or clarify. Not for artifact gap scans, planning, or code.

Productivity & Notes65

06 Product Brief

564

ai-driven-dev/framework

Produces a concise Product Brief before requirements. Use when the user wants to frame or revisit a product opportunity and how it will be validated. Not for requirements, technical design, or planning.

Productivity & Notes65

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.