Borrowing it
Nothing to install: this file belongs to egregore-labs/egregore. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/egregore-labs/egregore/main/.claude/skills/telemetry/SKILL.mdgit clone --depth 1 https://github.com/egregore-labs/egregoreWrote 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/egregore-labs/egregore/telemetry)<a href="https://agentmods.dev/skills/egregore-labs/egregore/telemetry"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/telemetry.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00042 | $0.00499 |
| Opus 5 | $0.00021 | $0.00249 |
| Sonnet 5 | $0.00008 | $0.00100 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
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 9d 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
Manage telemetry settings. Shows status by default.
When to invoke
User says: "/telemetry", "telemetry status", "turn off telemetry", "disable telemetry", "what data do you collect", "show my telemetry events", "clear telemetry buffer"
Not this: viewing telemetry across all registered orgs (internal, admin only) → /telemetry-admin
Arguments
status(default) — show whether telemetry is enabled, buffer size, opt-out methodoffordisable— disable telemetry (setstelemetry: falsein state file)onorenable— re-enable telemetryshow [N]— show last N buffered events (default 10)clear— delete local telemetry buffer
What to do
Parse the argument (default to status if none given).
status (default)
bash bin/telemetry.sh status
Show the output to the user.
off / disable
bash bin/telemetry.sh disable
Confirm: "Telemetry disabled. No events will be collected until you run /telemetry on."
on / enable
bash bin/telemetry.sh enable
Confirm: "Telemetry re-enabled."
show [N]
bash bin/telemetry.sh show ${N:-10}
Show the output. If empty, say "No buffered events."
clear
bash bin/telemetry.sh clear
Confirm: "Local telemetry buffer cleared."
What is collected
Only: command names, timestamps, session durations, error codes, branch names, query latencies.
What is NEVER collected
File paths, file contents, code, env var values, conversation content, command arguments that might contain user content.
Opt-out methods
/telemetry off— persistent opt-out via state fileEGREGORE_NO_TELEMETRY=1in.env— env var opt-outDO_NOT_TRACK=1— standard env var opt-out
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.
- 9d ago First seen · 78 lines · 42 tokens per session scan A 79d2ea25cabd
telemetry is a skill published in the GitHub repository egregore-labs/egregore (282 stars, last pushed 5d ago), licensed MIT. It adds 42 tokens to every session and 499 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
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
work
Execute an approved wish plan — orchestrate subagents per task group with fix loops, validation, and review handoff.
sw-do
Implement a SpecWeave increment task by task through the ledger, with evidence per task and a verified close. Use for "implement this", "start working", "continue the increment", "keep going".
done
Close an increment: ledger check, specweave verify, optional review, then specweave complete. Use when all tasks are done and saying "close increment", "we are done", or "finish up".
xiaohongshu-image-creator
An image-making assistant for Xiaohongshu, a Chinese social platform for lifestyle, product, and educational posts. It creates vertical covers and supporting images matched to the post’s topic, audience, and visual style.
atomic-tdd
Test-first discipline. Auto-triggers on "let's implement X", "add feature Y", "fix bug Z", "write a test for", "implement", "build out", and similar pre-code-change phrases. Iron rule: failing test exists before production code. Skip only for pure docs/config changes with an explicit "skipped because:" note. Explicit…