telemetry-change

A maintenance guide for changing telemetry, which is the data recorded about commands and requests, across authentication methods and network endpoints. It documents separate backend request markers and command-side AEM events.

In plain words
What is it for?
Use it when adding authentication domains, changing request headers or tracking fields, changing network exits, or investigating differences in command counts, success rates, versions, or backend channels.
Why use it?
It helps prevent misleading usage data when requests use different credentials, gateways, or URLs. It also clarifies which local command events are recorded even when no credentials are used.

Agent

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/modelstudioai/cli/telemetry-change
Clone the repo
git clone --depth 1 https://github.com/modelstudioai/cli
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,594 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.02594
Opus 5 $0.00000 $0.01297
Sonnet 5 $0.00000 $0.00519
Haiku 4.5 $0.00000 $0.00259

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

Security

Grade A, and why

telemetry-change 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.

docs/agents/telemetry-change.md · 166 lines

How it starts

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

埋点变更

触发条件

  • 调整 AEM 命令事件、事件字段或参数 allowlist
  • 调整 User-Agentx-dashscope-source-config 或其他后端渠道标识
  • 新增鉴权域、请求网关或绕开统一 Client 的网络出口
  • 排查命令量、成功率、版本、鉴权域或后端渠道数据不一致

当前数据流

三套鉴权对应三套请求域,但不代表三套网关使用相同的后端埋点。命令侧另有一套覆盖所有实际执行命令的 AEM 客户端事件,两者必须分开理解。

命令进入 run
  ├─ telemetryStage
  │    ├─ ~/.bailian/telemetry.jsonl
  │    └─ AEM(pid=bailian-cli-node, event name=命令路径)
  │
  └─ authStage
       ├─ apiKey  → DashScope / 模型域
       ├─ console → Bailian Console Gateway
       ├─ openapi → 阿里云 OpenAPI
       └─ none    → 无凭证域;本地命令也仍有 AEM 命令事件

1. 三套鉴权与埋点标识

命令声明 凭证 / 请求域 主要请求出口 后端埋点标识 前端埋点标识(AEM)
auth: "apiKey" API Key;DashScope / OpenAI-compatible 模型域 Client.request/requestJsonMcpClient、Managed Agent instrumented fetch、上传策略 有:User-Agentx-dashscope-source-config 有:pid=bailian-cli-nodeauthMethod=apiKey
auth: "console" Console access token;Bailian Console Gateway callConsoleGateway()/cli/api.json 有:pid=bailian-cli-nodeauthMethod=console
auth: "openapi" AccessKey ID/Secret,可选 STS token;阿里云 OpenAPI Client.openApiJson() 有:x-dashscope-source-config 有:pid=bailian-cli-nodeauthMethod=openapi
auth: "none" 无凭证域 本地逻辑或命令自行管理的登录/配置流程 有:pid=bailian-cli-nodeauthMethod=none

Read the full file on GitHub · 166 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 · 166 lines · 0 tokens per session scan A 0e3c2139b8ea

Subscribe to this mod's changes

telemetry-change is an agent published in the GitHub repository modelstudioai/cli (320 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,594 tokens. 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.