Borrowing it
Nothing to install: this file belongs to seasonedcc/discord-manager. 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/seasonedcc/discord-manager/main/.claude/skills/integration-telemetry/SKILL.mdgit clone --depth 1 https://github.com/seasonedcc/discord-managerWrote 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/seasonedcc/discord-manager/integration-telemetry)<a href="https://agentmods.dev/skills/seasonedcc/discord-manager/integration-telemetry"><img src="https://agentmods.dev/badge/skills/seasonedcc/discord-manager/integration-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/seasonedcc/discord-manager/integration-telemetry"><img src="https://agentmods.dev/badge/skills/seasonedcc/discord-manager/integration-telemetry.svg" alt="Reviewed on agentmods" width="80" 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.00094 | $0.02336 |
| Opus 5 | $0.00047 | $0.01168 |
| Sonnet 5 | $0.00019 | $0.00467 |
| Haiku 4.5 | $0.00009 | $0.00234 |
Grade A, and why
integration-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 10d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration telemetry
Everything here documents the repository as it is on main. If main disagrees with this file, main wins: follow it and flag the drift.
Every call this product makes to Discord is recorded, and every reading the owner sees is derived from those records. This is the standard those operations follow. Read the canonical implementations too — app/business/sending.server.ts and app/business/ingestion.server.ts write these families, and app/business/ingestion-status.server.ts derives the readings — the code is the standard; this file is the rules it follows.
Three families exist today, each with its own tables:
message_send_requests/message_send_deliveries/message_send_failures/message_send_skips— sends issued through MCPbackfill_runs/backfill_run_progress/backfill_run_completions/backfill_run_failures— REST history backfills and gap sweepsgateway_connections/gateway_disconnections— the daemon's link to Discord
Each operation owns its own tables
A new operation ships its own append-only tables — one request table plus one table per outcome — and its own reason vocabulary. Never build a generalized telemetry framework and never share a reason vocabulary across families: a shared vocabulary forces every operation to speak in the widest set of reasons any one of them needs, and a reason that cannot happen in this family would still typecheck in it.
Reasons are text columns with a check constraint listing the family's own values, paired with a TypeScript union in the domain's .common.ts. Load database-design and kysely before writing the migration.
Never widen an existing reason to cover a new case. A case the current reasons do not name gets its own reason, its own copy, and its own ruling on guidance.
Every path records exactly one outcome
Delivered, failed, and skipped are three different things, and skipped is never success. A send that never went out because the bot cannot post in the target channel records a skip with the reason that stopped it, not silence and not a delivery.
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.
- 10d ago First seen · 114 lines · 94 tokens per session scan A 5b6be9aecce4
integration-telemetry is a skill published in the GitHub repository seasonedcc/discord-manager (3 stars, last pushed 1mo ago), licensed MIT. It adds 94 tokens to every session and 2,336 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
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…