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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/egregore-labs/egregore/telemetry"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/telemetry.svg" alt="Reviewed on agentmods" width="80" 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.00046 | $0.00897 |
| Opus 5.5 | $0.00018 | $0.00359 |
| Sonnet 5.5 | $0.00009 | $0.00179 |
| Haiku 4.5 | $0.00005 | $0.00090 |
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 24d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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", "inspect/export/share 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 telemetryinspect [N]or legacyshow [N]— show last N buffered events (default 10)export <path>— validate and copy the local JSONL dataset; never uploadsshare— disclose the exact local dataset and prepare a short-lived confirmation tokenshare --confirm <token>— send only the unchanged, previously disclosed dataset to the same targetclear— 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."
inspect [N]
Use {count} for the number after inspect or show in the command's arguments, or 10 when omitted, escaping embedded single quotes as '\'':
bash bin/telemetry.sh inspect '{count}'
Show the output. If empty, say "No buffered events."
export
bash bin/telemetry.sh export "<path>"
Report the resulting local path. Export validates the same content-free event envelope used by sharing. It does not grant permission to upload the file.
share
First prepare the proposal. This performs no network I/O:
bash bin/telemetry.sh share
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.
- 24d ago Changed · +42 lines · +4 tokens per session 85cdf9025fcb
- 1mo ago First seen · 78 lines · 42 tokens per session scan A 79d2ea25cabd
telemetry is a skill published in the GitHub repository egregore-labs/egregore (293 stars, last pushed 9d ago), licensed MIT. It adds 46 tokens to every session and 897 once invoked, about $0.0002 per session on Opus 5.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
handoff-protocols
Manages work transitions between team members or agents by creating structured handoff documents, summarizing project status, documenting key decisions, blockers, and open questions, and generating onboarding briefs. Use when someone needs to hand off, hand over, or transition a project; pass work to another person or…
parallel-investigation
Coordinates parallel investigation threads to simultaneously explore multiple hypotheses or root causes across different system areas. Use when debugging production incidents, slow API performance, multi-system integration failures, or complex bugs where the root cause is unclear and multiple plausible theories exist…
structured-code-review
Performs a structured five-stage code review covering requirements compliance, correctness, code quality, testing, and security/performance. Each stage uses targeted checklists and categorized feedback (Blocker/Major/Minor/Nit) with actionable suggestions and rationale. Use when the user asks for code review, PR…
bothread
Join and behave correctly in a Bothread room — a shared, human-governed space where you collaborate with other AI agents on one codebase. Use this when the user says they want you to join a Bothread session, gives you a Bothread session ID, or asks you to coordinate with other agents.
git-workflow
Git branching, commit conventions, rebase vs merge, conflict resolution, and release tagging. Use when setting up a git workflow, writing commits, resolving conflicts, or preparing a release.
mflow
Use when working in a repo that uses mflow, coordinating multiple AI agents/worktrees, setting up mflow sync, installing mflow MCP in Codex/Claude Code/Cursor/opencode, or before git operations where synced file changes may affect commits. Applies to CLI, MCP, room secrets, pause/resume, locks, status checks, and safe…