Cost Tracking
affaan-m/ECC
Track and report Claude Code token usage, spending, and budgets from the local ECC cost-tracker metrics log.
Owns what a session cost and who it was for, under src/contexts/telemetry/ — reading a tool's own local files, attributing a figure to a person, a task, a flow or a step, and the sink that keeps…
MITAuto-check passed
Install Telemetry
$ npx skills add ai-driven-dev/framework --skill telemetry -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ai-driven-dev/framework telemetry --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ai-driven-dev/framework.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cli/.claude/skills/telemetry .claude/skills/telemetry && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "telemetry" agent skill from https://github.com/ai-driven-dev/framework/tree/main/cli/.claude/skills/telemetry into .claude/skills/telemetry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "telemetry", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ai-driven-dev/framework/tree/main/cli/.claude/skills/telemetryType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ai-driven-dev/framework --skill telemetry -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ai-driven-dev/framework telemetry --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ai-driven-dev/framework.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cli/.claude/skills/telemetry .agents/skills/telemetry && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "telemetry" agent skill from https://github.com/ai-driven-dev/framework/tree/main/cli/.claude/skills/telemetry into .agents/skills/telemetry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "telemetry", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ai-driven-dev/framework --skill telemetry -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ai-driven-dev/framework telemetry --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ai-driven-dev/framework.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cli/.claude/skills/telemetry .cursor/skills/telemetry && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "telemetry" agent skill from https://github.com/ai-driven-dev/framework/tree/main/cli/.claude/skills/telemetry into .cursor/skills/telemetry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "telemetry", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ai-driven-dev/framework.git --path cli/.claude/skills/telemetry--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ai-driven-dev/framework --skill telemetry -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ai-driven-dev/framework telemetry --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ai-driven-dev/framework.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cli/.claude/skills/telemetry .gemini/skills/telemetry && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "telemetry" agent skill from https://github.com/ai-driven-dev/framework/tree/main/cli/.claude/skills/telemetry into .gemini/skills/telemetry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "telemetry", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ai-driven-dev/framework telemetryInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ai-driven-dev/framework --skill telemetry -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ai-driven-dev/framework.git skills-src && mkdir -p .github/skills && cp -r skills-src/cli/.claude/skills/telemetry .github/skills/telemetry && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "telemetry" agent skill from https://github.com/ai-driven-dev/framework/tree/main/cli/.claude/skills/telemetry into .github/skills/telemetry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "telemetry", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ai-driven-dev/framework --skill telemetry -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ai-driven-dev/framework telemetry --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ai-driven-dev/framework.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cli/.claude/skills/telemetry .opencode/skills/telemetry && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "telemetry" agent skill from https://github.com/ai-driven-dev/framework/tree/main/cli/.claude/skills/telemetry into .opencode/skills/telemetry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "telemetry", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
telemetry- GitHub stars
- 513
- Token cost
- ~1.1k tokens
- SKILL.md length
- 488 words
- Files
- 1
- Skills in repo
- 46
- Repo updated
- First seen
- Licence
- MIT
At a glance
Owns what a session cost and who it was for, under src/contexts/telemetry/ — reading a tool's own local files, attributing a figure to a person, a task, a flow or a step, and the sink that keeps…
- Adding a reader for another tools transcript format
- SKILL.md covers What goes in, How, Public surface and How it's tested
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Changing how a figure is attributed
What it does
Telemetry is an agent skill from ai-driven-dev/framework. Owns what a session cost and who it was for, under src/contexts/telemetry/ — reading a tool's own local files, attributing a figure to a person, a task, a flow or a step, and the sink that keeps records per machine. Use when adding a reader for another tool's transcript format, changing how a figure is attributed or reported, touching the sink or the identity store, or wiring a telemetry port. Do NOT use for what a tool declares about being measured — that is kernel/measurement.ts, read via the tools skill. Do…
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Marketplace Framework AI-Driven Dev : Context Engineering, Plugins, Agents, Skills, Hooks, Templates, SDLC. The licence is MIT.
When your agent uses it
- Adding a reader for another tools transcript format
- Changing how a figure is attributed
- Touching the sink
- The identity store
Example prompts
- “/telemetry”
What it can do on your machine
Read from SKILL.md and the folder at commit 6e30640. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Telemetry loads about 1.1k tokens when it runs. Until then it costs about 164 tokens; SKILL.md has 488 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ai-driven-dev/framework at commit 6e30640, republished under its MIT licence (© ai-driven-dev). 488 words, ~1,093 tokens.
Download SKILL.mdSave it as
.claude/skills/telemetry/SKILL.md (or your agent's skills folder).- name
- telemetry
- description
- Owns what a session cost and who it was for, under src/contexts/telemetry/ — reading a tool's own local files, attributing a figure to a person, a task, a flow or a step, and the sink that keeps records per machine. Use when adding a reader for another tool's transcript format, changing how a figure is attributed or reported, touching the sink or the identity store, or wiring a telemetry port. Do NOT use for what a tool declares about being measured — that is `kernel/measurement.ts`, read via the `tools` skill. Do NOT use for installing or removing the hook that writes the run journal into a project — that record belongs to `framework`.
Telemetry
telemetry answers two questions about work already done: what did it cost, and whose was it.
It never causes the work and never installs anything on a project's behalf. Everything it reads
already exists on disk because a tool wrote it, so the whole context is a set of readers, a set
of attribution rules, and one sink.
Where the sink and the run journal live, what the report renders, and what each tool declares
about being measured are in aidd_docs/memory/telemetry.md. Read that for the facts; this page
says where new code goes and what it must not do.
What goes in
| Concept | Location |
|---|---|
| A rendered answer's shape | domain/cost-report.ts, domain/cost-report-envelope.ts |
| How a figure is tied to something | domain/step-attribution.ts, domain/task-attribution.ts, domain/flow-attribution.ts |
| Reading one tool's own file format | domain/formats/ (one module per tool's transcript or export) |
| A stored record and what happens to it over time | domain/telemetry-sink-record.ts, domain/telemetry-sink-retention.ts |
| Who a session was for, and how strongly that is known | domain/person-resolution.ts, domain/ports/person-identity-reader.ts, domain/ports/person-identity-store.ts |
| Something telemetry needs from outside itself | domain/ports/ — declared here, satisfied at the composition root |
| The concrete reader behind one of those ports | infrastructure/ |
One question the aidd telemetry command asks | application/ |
How
- A tool declares, telemetry reads. What a route was measured to supply, and where a tool's
transcripts live, are declared in
kernel/measurement.tsand filled in per tool undercontexts/tools/domain/profiles/<tool>/. Every field there is required on purpose: a default would be a capability nobody measured, quietly asserted for a tool nobody looked at. Never add a branch on a tool id inside this context. - What telemetry needs from another context, it declares as its own port.
installed-plugins-reader.tsandignore-entries.tsare the pattern: telemetry states the question,runtime/wiring/telemetry.tshands it an answer, and no context reaches into telemetry in return. - A figure with no established denomination is not an amount. A zero whose denomination was never established, a credit and a premium request are each their own thing; conflating them is how a report lies without ever being wrong about a number.
- An interval derived from the run journal is this CLI's inference, not the tool's statement.
Keep the two distinguishable in whatever you add —
toolStatedStepexists for exactly that. - Follow the use-case and port/adapter rules in
.claude/rules/00-architecture/.
Show full SKILL.md (119 more words)Show less
Public surface
tests/architecture/context-boundary.arch.test.ts holds the list (PUBLIC_MODULES.telemetry):
the use cases the telemetry command drives, the shapes a rendered answer is made of, the
commit-trailer format the git adapter writes, and the two ports a caller wires a concrete
adapter into (domain/ports/telemetry-sink.ts, domain/ports/version-control.ts). Nothing
else, and no adapter. Rendering happens in presentation/display/, never here.
How it's tested
tests/contexts/telemetry/mirrorssrc/contexts/telemetry/— a format reader and an attribution rule are unit-tier; an adapter against a real temp filesystem is integration-tier.- A reader for a new tool's format needs a fixture captured from that tool's real output. A
format module tested only against a fixture this repository wrote proves the parser, not the
format. See the
testskill before touching a golden snapshot.
© ai-driven-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in cli/.claude/skills/telemetry of ai-driven-dev/framework.
Open the folder on GitHubat commit 6e30640
Compare with similar skills
Telemetry next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Telemetry this skillai-driven-dev/framework | 513 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Cost Trackingaffaan-m/ECC | 275k | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Cost Exportruvnet/ruflo | 74k | 1 repos | ~687 | Automated safety check: Notes | MIT | |
| Cost Conversationruvnet/ruflo | 74k | — | ~407 | Automated safety check: Notes | MIT | |
| Cost Reportruvnet/ruflo | 74k | 1 repos | ~830 | Automated safety check: Notes | MIT | |
| Cost Optimizeruvnet/ruflo | 74k | 1 repos | ~997 | Automated safety check: Notes | MIT |
Similar skills
Cost Export
ruvnet/ruflo
Export cost-tracking telemetry in Prometheus textfile or webhook JSON formats — for external observability (Grafana, Datadog, custom dashboards)
Cost Conversation
ruvnet/ruflo
Per-conversation cost view — list every session in cost-tracking with started-at, message count, top model, and total cost
Cost Report
ruvnet/ruflo
Generate a cost report showing token usage and USD costs by agent and model
Cost Optimize
ruvnet/ruflo
Analyze token usage patterns and recommend cost optimizations with estimated savings
Cost Track
ruvnet/ruflo
Auto-capture per-session token usage from the Claude Code session jsonl and persist to the cost-tracking namespace
More from ai-driven-dev/framework
All 46 skills in this repo00 Async Dev
ai-driven-dev/framework
Drive the async-dev pipeline from one entry point, whether setup, run, or review.
01 Plan
ai-driven-dev/framework
Turn a request, ticket, or file into a phased implementation plan.
01 Sdlc
ai-driven-dev/framework
Autonomously orchestrates a request from framing to a draft pull request, isolating implementation, independent review, and final outcome challenge.
02 Backlog
ai-driven-dev/framework
Orchestrates a product backlog end to end. An agent skill from ai-driven-dev/framework.
00 Onboard
ai-driven-dev/framework
Guide a project's journey through AIDD, from first setup to shipping a feature.
01 Acceptance QA
ai-driven-dev/framework
Validate a reviewed candidate's observable behavior against its acceptance criteria and record short named videos as reviewer evidence.
Questions about Telemetry
What does Telemetry do?
Owns what a session cost and who it was for, under src/contexts/telemetry/ — reading a tool's own local files, attributing a figure to a person, a task, a flow or a step, and the sink that keeps…. Telemetry is an agent skill from ai-driven-dev/framework. Owns what a session cost and who it was for, under src/contexts/telemetry/ — reading a tool's own local files, attributing a figure to a person, a task, a flow or a step, and the sink that keeps records per machine.
When should I use Telemetry?
Telemetry fits situations like: adding a reader for another tools transcript format; changing how a figure is attributed; touching the sink; the identity store.
How do I install Telemetry in Claude Code?
Run `npx skills add ai-driven-dev/framework --skill telemetry -a claude-code`. Or copy the skill folder (cli/.claude/skills/telemetry in ai-driven-dev/framework) into .claude/skills/telemetry in your project. Claude Code loads it when a task matches its description.
How do I install Telemetry in Codex?
Run `npx skills add ai-driven-dev/framework --skill telemetry -a codex`. Or copy the skill folder (cli/.claude/skills/telemetry in ai-driven-dev/framework) into .agents/skills/telemetry in your project. Codex loads it when a task matches its description.
Can I use Telemetry in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ai-driven-dev/framework --skill telemetry -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/telemetry, .gemini/skills/telemetry, .github/skills/telemetry and .opencode/skills/telemetry in your project.
What does Telemetry need to run?
SKILL.md names no scripts, command-line tools or credentials: Telemetry is instructions for the agent only.
Does Telemetry access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Telemetry safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Telemetry use?
Telemetry is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Telemetry use?
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Telemetry?
Skills that share tags, products or a category with Telemetry: Cost Tracking (affaan-m/ECC, 275k stars), Cost Export (ruvnet/ruflo, 74k stars), Cost Conversation (ruvnet/ruflo, 74k stars) and Cost Report (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Telemetry?
ai-driven-dev (a GitHub organization) maintains it in ai-driven-dev/framework, which has 513 GitHub stars. The repository holds 46 skills in this directory. The repository was last updated on October 8, 2026.
Source: ai-driven-dev/framework on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.