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 agentmods add instructions/malwarebo/nyrve/telemetrygit clone --depth 1 https://github.com/malwarebo/nyrveWhat 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 | $0.00979 | $0.00979 |
| Opus 5 | $0.00490 | $0.00490 |
| Sonnet 5 | $0.00196 | $0.00196 |
| Haiku 4.5 | $0.00098 | $0.00098 |
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.
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.
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
});
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.
- 2d ago First seen · 114 lines · 979 tokens per session scan A f5956e1fc706
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.
Other instructions, from other repositories
bb AGENTS.md
AGENTS.md instructions for get-bb/bb, covering codebase guidelines, simplicity first, code comments, types and contracts and server and daemon.
vibeyard CLAUDE.md
Claude Code instructions for elirantutia/vibeyard, covering claude.md, what this is, build & run, testing and architecture.
nimbalyst AGENTS.md
AGENTS.md instructions for nimbalyst/nimbalyst: At the beginning of every AI session, read the root CLAUDE.md and any applicable package-level CLAUDE.md before taking actions.
coder CLAUDE.md
Claude Code instructions for coder/coder, a project described as: Secure environments for developers and their agents.
dockside CLAUDE.md
Instructions for newsnowlabs/dockside, covering repo notes, the dockside cli, session setup, ad-hoc http checks and integration suite invocation (local mode).
nezha AGENTS.md
AGENTS.md instructions for hanshuaikang/nezha, covering nezha — agents.md, 项目概述, 开发命令, 架构设计 and 前端(src/).