nyrve telemetry.instructions.md

A set of rules for recording telemetry events in VS Code while classifying data for privacy and GDPR compliance. Telemetry is usage and performance data sent by software to its developers.

In plain words
What is it for?
Use it when adding feature-use, performance, or error telemetry events to a VS Code extension.
Why use it?
It helps developers describe event data consistently, protect user privacy, and keep event types safe in TypeScript.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/malwarebo/nyrve/telemetry
Clone the repo
git clone --depth 1 https://github.com/malwarebo/nyrve

Made for: GitHub Copilot.

Per session 979 This file is loaded in full into every session.
When invoked 979 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00979 $0.00979
Opus 5 $0.00490 $0.00490
Sonnet 5 $0.00196 $0.00196
Haiku 4.5 $0.00098 $0.00098

Measured 2d ago against content hash f5956e1fc706, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

nyrve telemetry.instructions.md 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 2d 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.

Origin

This is a copy

100% identical to vscode telemetry.instructions.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.github/instructions/telemetry.instructions.md · 114 lines

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.

Patterns for GDPR-compliant telemetry in VS Code with proper type safety and privacy protection.

Implementation Pattern

1. Define Types

type MyFeatureEvent = {
    action: string;
    duration: number;
    success: boolean;
    errorCode?: string;
};

type MyFeatureClassification = {
    action: { classification: 'SystemMetaData'; purpose: 'FeatureInsight'; comment: 'The action performed.' };
    duration: { classification: 'SystemMetaData'; purpose: 'PerformanceAndHealth'; isMeasurement: true; comment: 'Time in milliseconds.' };
    success: { classification: 'SystemMetaData'; purpose: 'FeatureInsight'; isMeasurement: true; comment: 'Whether action succeeded.' };
    errorCode: { classification: 'SystemMetaData'; purpose: 'PerformanceAndHealth'; comment: 'Error code if action failed.' };
    owner: 'yourGitHubUsername';
    comment: 'Tracks MyFeature usage and performance.';
};

2.1. Send Event

this.telemetryService.publicLog2<MyFeatureEvent, MyFeatureClassification>('myFeatureAction', {
    action: 'buttonClick',
    duration: 150,
    success: true
});

2.2. Error Events

For error-specific telemetry with stack traces or error messages:

type MyErrorEvent = {
    operation: string;
    errorMessage: string;
    duration?: number;
};

type MyErrorClassification = {
    operation: { classification: 'SystemMetaData'; purpose: 'PerformanceAndHealth'; comment: 'The operation that failed.' };
    errorMessage: { classification: 'CallstackOrException'; purpose: 'PerformanceAndHealth'; comment: 'The error message.' };
    duration: { classification: 'SystemMetaData'; purpose: 'PerformanceAndHealth'; isMeasurement: true; comment: 'Time until failure.' };
    owner: 'yourGitHubUsername';
    comment: 'Tracks MyFeature errors for reliability.';
};

this.telemetryService.publicLogError2<MyErrorEvent, MyErrorClassification>('myFeatureError', {
    operation: 'fileRead',
    errorMessage: error.message,
    duration: 1200
});

Read the full file on GitHub · 114 lines

Changes

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.

  1. 2d ago First seen · 114 lines · 979 tokens per session scan A f5956e1fc706

Subscribe to this mod's changes

nyrve telemetry.instructions.md is an instructions file published in the GitHub repository malwarebo/nyrve (5 stars, last pushed 2mo ago), licensed MIT. It adds 979 tokens to every session, about $0.0049 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to vscode telemetry.instructions.md, differing in 0 lines, and is treated as a copy.