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 ALTEN-group/coding-pal --skill telemetry-scangit clone --depth 1 https://github.com/ALTEN-group/coding-palWrote 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/alten-group/coding-pal/telemetry-scan)<a href="https://agentmods.dev/skills/alten-group/coding-pal/telemetry-scan"><img src="https://agentmods.dev/badge/skills/alten-group/coding-pal/telemetry-scan/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/alten-group/coding-pal/telemetry-scan"><img src="https://agentmods.dev/badge/skills/alten-group/coding-pal/telemetry-scan.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.00091 | $0.00636 |
| Opus 5.5 | $0.00036 | $0.00254 |
| Sonnet 5.5 | $0.00018 | $0.00127 |
| Haiku 4.5 | $0.00009 | $0.00064 |
Grade A, and why
telemetry-scan 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 4d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Telemetry Scan
Compare live signals with a baseline and thresholds before customers notice. The scan reads exported series, so the same input always gives the same findings. Monitoring informs; humans act.
When to Use This Skill
- Learn is asked to watch a release: error rate creeping up, saturation approaching, cost drifting.
- A signal looks odd and the question is which deploy preceded it.
- CI should alert on a high severity signal in an exported metrics file.
- The weekly review needs the findings that may become Triage issues.
Path resolution
Resolve references/ and scripts/ relative to this skill's install directory (the folder that contains this SKILL.md), not the consumer repository root or the current shell cwd. If the skill was installed under .agents/skills/telemetry-scan/ or .claude/skills/telemetry-scan/, use that base path.
Workflow
- Read
references/telemetry-scan-contract.mdnow. It defines the input files, the finding rules, and the exit codes. - Get exports from the user or the pipeline (series, optionally baseline, thresholds, and deploys). Never query or log in to a production system, and never ask for production credentials.
- Run the scan from this skill's directory:
node scripts/telemetry-scan.mjs --series series.json --thresholds thresholds.json \
--deploys deploys.json --horizon-minutes 120
node scripts/telemetry-scan.mjs --series series.json --thresholds thresholds.json --json > findings.json
- Detect: report each finding with its numbers. Explain: for each finding, read the listed deploys and diffs, correlate with the logs and traces the user supplies, and propose a likely cause. State clearly that the QA and maintainer confirms the cause.
- Act (human): the QA and maintainer decides whether to mitigate. Hand
findings.jsonto thelearn-signalsskill to open Triage issues for thehighfindings.
Exit codes: 0 scanned, 1 invalid input, 3 at least one high finding (CI alerts on it).
What ships with it
4 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.
- 4d ago First seen · 44 lines · 91 tokens per session scan A abd7d2a77779
telemetry-scan is a skill published in the GitHub repository ALTEN-group/coding-pal (5 stars, last pushed 5d ago), licensed MIT. It adds 91 tokens to every session and 636 once invoked, about $0.0004 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-10-14.
Other skills, from other repositories
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…
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.