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.
npx agentmods add skills/agenkin/telemetrydeck-analytics/analyticsnpx skills add agenkin/telemetrydeck-analytics --skill analyticsgit clone --depth 1 https://github.com/agenkin/telemetrydeck-analyticsWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00109 | $0.04186 |
| Opus 5 | $0.00055 | $0.02093 |
| Sonnet 5 | $0.00022 | $0.00837 |
| Haiku 4.5 | $0.00011 | $0.00419 |
Grade A, and why
telemetrydeck-analytics 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.
How it starts
The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TelemetryDeck Analytics
Answers product-analytics questions against the TelemetryDeck v3 API via the bundled tdq CLI. Stdlib-only, cross-platform, OS-native secret storage, no .env, no repo-local files.
This skill ships as part of the telemetrydeck-analytics Claude plugin. While the plugin is enabled, the tdq wrapper is on PATH, so you can call it directly as tdq <subcommand>. If the wrapper isn't available (e.g. running outside Claude Code), fall back to python3 "$SKILL_DIR/tdq.py" <subcommand>.
User-invokable slash skills
The plugin exposes focused slash commands for common tasks — prefer them when the user's intent maps cleanly to one:
| Slash command | What it does |
|---|---|
/telemetrydeck-analytics:setup |
First-run login + app picker. |
/telemetrydeck-analytics:doctor |
End-to-end health check. |
/telemetrydeck-analytics:apps [list|use|add|remove|refresh] |
Manage registered apps. |
/telemetrydeck-analytics:dau [args] |
Daily active users. |
/telemetrydeck-analytics:mau [args] |
Monthly active users. |
/telemetrydeck-analytics:groupby <dim> [args] |
Breakdown by a dimension. |
/telemetrydeck-analytics:events |
Schema discovery (7d + 30d event counts). |
/telemetrydeck-analytics:signals [args] |
Top-N events, raw pipeline triage. |
/telemetrydeck-analytics:query <file or TQL> |
Run raw TQL. |
/telemetrydeck-analytics:report <question> |
Generate a markdown analytics report. |
This main skill handles the ambient / conversational case ("is the Pro share growing?", "why aren't signals arriving?") — it's model-invoked when a question needs analytics but doesn't match a slash command exactly.
First-run setup (once per machine)
tdq login
Prompts for email and password, mints a bearer, then lists the apps on your TelemetryDeck account and asks you to pick one. No need to know the app UUID up front. If the listing endpoint isn't exposed for your account, the CLI falls back to a manual UUID prompt.
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 239 lines · 109 tokens per session scan A 8d6a61819d07
telemetrydeck-analytics is a skill published in the GitHub repository agenkin/telemetrydeck-analytics (2 stars, last pushed 4mo ago), licensed MIT. It adds 109 tokens to every session and 4,186 once invoked, about $0.0005 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.
Other skills, from other repositories
motion-canvas
Motion Canvas framework reference covering project setup, core concepts (generators, signals, refs, scene hierarchy, timing, utilities), and 2D components (shapes, paths, text, media, layout, camera, transitions, custom components). Use when building or editing Motion Canvas scenes.
motion-canvas-agent
Agent tooling for Motion Canvas — seek, screenshot, scene graph inspection, settings control, and rendering via HTTP API. Requires a browser with the editor open.
animation-basics
Animation theory covering the 12 principles of animation and timing guidance. Use when designing motion, choosing easing approaches, or improving animation quality.
add-tool
Generate a correctly formatted AgenticStack tool file ready to submit as a pull request.
setup-tool
Given what the user wants to add to their app, pick the right tool and explain how to get started — no comparison needed.
recommend-tool
Recommend the best developer tool for your requirements using AgenticStack data.