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 skills add agenkin/telemetrydeck-analytics --skill signalsgit clone --depth 1 https://github.com/agenkin/telemetrydeck-analyticsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/agenkin/telemetrydeck-analytics/signals)<a href="https://agentmods.dev/skills/agenkin/telemetrydeck-analytics/signals"><img src="https://agentmods.dev/badge/skills/agenkin/telemetrydeck-analytics/signals.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00022 | $0.00186 |
| Opus 5 | $0.00011 | $0.00093 |
| Sonnet 5 | $0.00004 | $0.00037 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
signals 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 6d 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.
What it actually says
Signals
Print the top-N events by count for a rolling window. Use when the question is "what's happening in the pipeline right now?" rather than a specific analytical cut.
tdq signals $ARGUMENTS
Defaults: last 30 days, top 25.
Examples:
- "What's firing today?" →
tdq signals --days 1 --top 25 - "Top 50 events last week" →
tdq signals --days 7 --top 50
For schema discovery (which events EVER fire, with both 7d and 30d windows) prefer /telemetrydeck-analytics:events — it's more comparative. signals is for a single-window raw look.
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.
- 6d ago First seen · 21 lines · 22 tokens per session scan A 777eb33a1bb2
signals is a skill published in the GitHub repository agenkin/telemetrydeck-analytics (2 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 186 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.
Other skills, from other repositories
onboarding
Skill "onboarding" from knitli/toolshed, covering codeweaver first-run onboarding, your goal, setup flow, 1. welcome & overview and 2. embedding provider selection.
setup
Skill "setup" from knitli/toolshed, covering codeweaver setup / reconfiguration, your goal, setup flow, 1. welcome & context and 2. embedding provider selection.
specmint-core
Persistent spec management for AI coding workflows. Use this skill when the user explicitly mentions specs, forging, or structured planning: says "forge", "forge a spec", "write a spec for X", "create a spec", "plan X as a spec", "resume", "what was I working on", "spec list/status/pause/switch/activate", "implement…
.codex
Skill ".codex" from knitli/toolshed, covering context hygiene skill, name, description, instructions and 1. discovery.
beat-sync-video-editing
This skill should be used when the user asks to "edit a video to music", "create a beat-synced edit", "make a montage", "sync cuts to beats", "cut a video to the beat", "make a music video edit", "edit clips to a song", "build FFmpeg filters for video editing", or mentions combining video clips with audio tracks using…
make-montage
Build a beat-synced video montage from a video and audio file by orchestrating cadence's MCP tools. Use when the user asks to create a montage, edit action footage to music, or cut video to the beat.