setup

A first-run setup guide for the TelemetryDeck analytics command-line tool, which measures app usage. It explains how to log in, choose an app, and verify the saved access token.

In plain words
What is it for?
Setting up TelemetryDeck credentials, selecting an app, handling first-time or repeat setup, and checking that the login still works.
Why use it?
The login process needs an interactive terminal, which a coding agent's command runner does not provide. The guide explains what to do when that interaction cannot happen automatically.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/agenkin/telemetrydeck-analytics/setup
Any agent
npx skills add agenkin/telemetrydeck-analytics --skill setup
Clone the repo
git clone --depth 1 https://github.com/agenkin/telemetrydeck-analytics

Made for: Claude Code, Codex.

Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 393 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00029 $0.00393
Opus 5 $0.00015 $0.00197
Sonnet 5 $0.00006 $0.00079
Haiku 4.5 $0.00003 $0.00039

Measured 2d ago against content hash 92ec65a109f3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

setup scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/setup/SKILL.md · 49 lines

What it actually says

Setup

tdq login requires a real TTY for interactive prompts. Claude Code's Bash tool is not a TTY, so attempt the login and handle the two cases:

Case 1 — credentials not yet stored (first run)

Running tdq login via Bash will fail with:

stdin is not a TTY — cannot prompt for email.
Run `tdq login` directly in your terminal.

Tell the user: open a terminal and run tdq login. Walk them through what to expect:

  1. TelemetryDeck email prompt
  2. Password prompt (hidden)
  3. Numbered app picker — type the number next to their app and press Enter
  4. A login summary is printed on success

Once they confirm it completed, run tdq doctor via Bash to verify the token is live.

Case 2 — credentials already stored, only app selection needed

If email + password are already in the keychain (e.g. re-setup after switching apps), the non-TTY error will be on the app picker step. The CLI prints the app list before exiting. Read the app names and UUIDs from the error output and ask the user which app to use. Then run:

tdq login --app-id <chosen-uuid>

--app-id skips the picker entirely and works non-interactively.

Case 3 — $ARGUMENTS contains a UUID

Skip the picker immediately:

tdq login --app-id $ARGUMENTS

After any successful login

Run tdq doctor and relay the output so the user sees the end-to-end health check pass.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 49 lines · 29 tokens per session scan A 92ec65a109f3

Subscribe to this mod's changes

setup is a skill published in the GitHub repository agenkin/telemetrydeck-analytics (2 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 393 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.