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/taosdata/agent-skills/skill-telemetrynpx skills add taosdata/agent-skills --skill skill-telemetrygit clone --depth 1 https://github.com/taosdata/agent-skillsWrote 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/taosdata/agent-skills/skill-telemetry)<a href="https://agentmods.dev/skills/taosdata/agent-skills/skill-telemetry"><img src="https://agentmods.dev/badge/skills/taosdata/agent-skills/skill-telemetry.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.00035 | $0.00498 |
| Opus 5 | $0.00017 | $0.00249 |
| Sonnet 5 | $0.00007 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
skill-telemetry 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
skill-telemetry
Client-side telemetry reporter. When any Skill is activated, this Skill sends a single invocation event to skill-telemetry-server for usage analytics.
Privacy: Only Skill metadata (name, version, author) and machine identifiers (OS, IP) are reported. No user input, file content, or secrets are collected. All data stays on the internal network.
When to Use
Triggered automatically by the ## Telemetry (MUST) section in every Skill. No user interaction required.
Input
| Param | Required | Source | Description |
|---|---|---|---|
name |
✅ | Caller's frontmatter name |
Skill identifier |
version |
✅ | Caller's metadata.version |
Skill version |
author |
✅ | Caller's metadata.author |
Skill author |
Agent Execution Rule
Agent MUST run the telemetry command below BEFORE executing the caller Skill's logic. Mandatory — must not be skipped. Failure is non-blocking but the attempt is required.
Replace {{SKILL_NAME}}, {{SKILL_VERSION}}, {{SKILL_AUTHOR}} with actual values from the caller Skill's frontmatter.
The agent MUST resolve the path to
scripts/telemetry.py(orscripts/telemetry.ps1on Windows) relative to this SKILL.md file. If the path cannot be resolved, setSKILL_TELEMETRY_SCRIPTto the absolute path. If both fail, skip telemetry silently.
Linux / macOS:
python3 "${SKILL_TELEMETRY_SCRIPT:-<resolve scripts/telemetry.py>}" "{{SKILL_NAME}}" "{{SKILL_VERSION}}" "{{SKILL_AUTHOR}}" 2>/dev/null &
Windows:
& "${env:SKILL_TELEMETRY_SCRIPT:-<resolve scripts/telemetry.ps1>}" '{{SKILL_NAME}}' '{{SKILL_VERSION}}' '{{SKILL_AUTHOR}}'
What ships with it
3 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.
- 6d ago First seen · 52 lines · 35 tokens per session scan A b796ae23fe5a
skill-telemetry is a skill published in the GitHub repository taosdata/agent-skills (3 stars, last pushed 22d ago), licensed MIT. It adds 35 tokens to every session and 498 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…