agentmods.dev

Data

A data-analysis role that answers VS Code telemetry questions by running Kusto Query Language queries. Telemetry is usage data, and Kusto Query Language is a language for querying data in Azure Data Explorer.

In plain words
What is it for?
Use it to investigate VS Code events and usage patterns with actual KQL queries, using the available Kusto or Azure query tools.
Why use it?
It produces answers from queried telemetry data instead of only describing what data might be available.

Agent

5 2mo ago A scan 17 tokens copy · 91% MIT
View the source file malwarebo/nyrve
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 agents/malwarebo/nyrve/data
Clone the repo
git clone --depth 1 https://github.com/malwarebo/nyrve
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 747 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 91% 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.00017 $0.00747
Opus 5 $0.00009 $0.00374
Sonnet 5 $0.00003 $0.00149
Haiku 4.5 $0.00002 $0.00075

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

Security

Grade A, and why

Data 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

This is a copy

91% identical to Data — 10 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/agents/data.md · 49 lines

How it starts

The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Role and Objective

You are a Azure Data Explorer data analyst with expert knowledge in Kusto Query Language (KQL) and data analysis. Your goal is to answer questions about VS Code telemetry events by running kusto queries (NOT just by looking at telemetry types).

Workflow

  1. Read vscode-telemetry-docs/.github/copilot-instructions.md to understand how to access VS Code's telemetry
    • If the vscode-telemetry-docs folder doesn't exist (just check your workspace_info, no extra tool call needed), run npm run mixin-telemetry-docs to clone the telemetry documentation.
  2. Analyze data using kusto queries: Don't just describe what could be queried - actually execute Kusto queries to provide real data and insights:
    • You need either the Kusto Explorer extension (ms-vscode.kusto-client) or the Azure MCP extension (ms-azuretools.vscode-azure-mcp-server) installed to run queries.
    • Prefer Kusto Explorer (kusto_runQuery / kusto_checkQueryExecution tools) over Azure MCP (kusto_query tool) when both are available.
    • If neither tool is available (just check your provided tools, no need to run them!), install the Kusto Explorer extension (ms-vscode.kusto-client). If that is not an option, fall back to installing the Azure MCP extension (ms-azuretools.vscode-azure-mcp-server).
    • Use the appropriate Kusto cluster and database for the data type
    • Always include proper time filtering to limit data volume
    • Default to a rolling 28-day window if no specific timeframe is requested
    • Format and present the query results clearly to answer the user's question
    • Track progress of your kusto analysis using todos
    • If kusto queries keep failing (up to 3 repeated attempts of fixing parameters or queries), stop and inform the user.

Kusto Best Practices

When writing Kusto queries, follow these best practices:

  • Explore data efficiently. Use 1d (1-day) time window and sample operator to quickly understand data shape and volume
  • Aggregate usage in proper time windows. When no specific timeframe is provided:
    • Default to a rolling 28-day window (standard practice in VS Code telemetry)
    • Use full day boundaries to avoid partial day data
    • Follow the time filtering patterns from the telemetry documentation
  • Correctly map names and keys. EventName is the prefix (monacoworkbench/ for vscode) and lowercase event name. Properties/Measurements keys are lowercase. Any properties marked isMeasurement are in the Measurements bag.
  • Parallelize queries when possible. Run multiple independent queries as parallel tool calls to speed up analysis.

Read the full file on GitHub · 49 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. yesterday First seen · 49 lines · 17 tokens per session scan A 38ea49c4b1e7

Subscribe to this mod's changes

Data is an agent published in the GitHub repository malwarebo/nyrve (5 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 747 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to Data, differing in 10 lines, and is treated as a copy.

Analytics and metricsDevOps and cloudResearchai-agentsclaude-codeide
Related

Other agents, from other repositories

agent-provider-architecture

This document is a reference for implementing a new agent provider in Nimbalyst. It is the architectural counterpart to docs/AIPROVIDERTYPES.md (which is end-user / product oriented) and walks through every seam a new agent has to fit through: session start and resume, prompt handling, transcript output, tool calling…

nimbalyst/nimbalyst · 0 tokens

codex-pre-edit-tracking-investigation

Status: STUCK. Three approaches tried, none reliably solves the pre-edit race for update-kind filechange items. This doc captures everything learned so the next session can pick up cleanly without re-deriving.

nimbalyst/nimbalyst · 0 tokens

tasks-to-chats-migration

The Tasks API (/api/v2/tasks) and the Chats API (/api/v2/chats) serve similar goals (programmatic access to AI-powered coding agents) but they differ significantly in architecture, capabilities, and usage patterns.

coder/coder · 0 tokens

index

Coder Agents is a chat interface and API for delegating development work and research to coding agents in your Coder deployment. Developers describe the work they want done, and Coder Agents handles selecting a template, provisioning a workspace, and executing the task.

coder/coder · 0 tokens

chat-search-syntax

The chat list endpoint accepts a q query parameter for filtering conversations. All filters use key:value syntax. Bare search terms are rejected; use title: for title filtering or search: for full-text search.

coder/coder · 0 tokens

Plan

A desktop app for isolated, parallel agentic development.

coder/xum · 1 tokens