vscode kusto.instructions.md

Instructions for exploring Visual Studio Code telemetry with Kusto, a query language used to analyze large datasets.

In plain words
What is it for?
Use them when writing Kusto queries or analyzing Visual Studio Code telemetry and other collected usage data.
Why use it?
They point to the relevant cluster, database, schema, and query patterns, reducing errors when investigating telemetry.

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/microsoft/vscode/kusto
Clone the repo
git clone --depth 1 https://github.com/microsoft/vscode

Made for: GitHub Copilot.

Per session 183 This file is loaded in full into every session.
When invoked 183 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.00183 $0.00183
Opus 5 $0.00092 $0.00092
Sonnet 5 $0.00037 $0.00037
Haiku 4.5 $0.00018 $0.00018

Measured yesterday against content hash 609bde2e8a76, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

vscode kusto.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 yesterday.

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

Copies of this mod

1 near-identical copy found in the catalogue:

.github/instructions/kusto.instructions.md · 20 lines

What it actually says

Kusto Exploration Instructions

When performing Kusto queries, telemetry analysis, or data exploration tasks for VS Code, consult the comprehensive Kusto instructions located at:

kusto-vscode-instructions.md

These instructions contain valuable information about:

  • Available Kusto clusters and databases for VS Code telemetry
  • Common query patterns and best practices
  • Schema information and table structures
  • Tips for effective data exploration

Reading these instructions before writing Kusto queries will help you write more accurate and efficient queries, avoid common pitfalls, and leverage existing knowledge about VS Code's telemetry infrastructure.

(Make sure to have the main branch of vscode-tools up to date in case there are problems and the repository cloned from https://github.com/microsoft/vscode-tools).

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. yesterday First seen · 20 lines · 183 tokens per session scan A 609bde2e8a76

Subscribe to this mod's changes

vscode kusto.instructions.md is an instructions file published in the GitHub repository microsoft/vscode (190,061 stars, last pushed yesterday), licensed MIT. It adds 183 tokens to every session, about $0.0009 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-30.