Borrowing it
Nothing to install: this file belongs to Mizune/llm-cli-telemetry. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Mizune/llm-cli-telemetry/main/CLAUDE.mdgit clone --depth 1 https://github.com/Mizune/llm-cli-telemetryWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/mizune/llm-cli-telemetry/claude-md)<a href="https://agentmods.dev/instructions/mizune/llm-cli-telemetry/claude-md"><img src="https://agentmods.dev/badge/instructions/mizune/llm-cli-telemetry/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/mizune/llm-cli-telemetry/claude-md"><img src="https://agentmods.dev/badge/instructions/mizune/llm-cli-telemetry/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.01192 | $0.01192 |
| Opus 5.5 | $0.00477 | $0.00477 |
| Sonnet 5.5 | $0.00238 | $0.00238 |
| Haiku 4.5 | $0.00119 | $0.00119 |
Grade B, and why
llm-cli-telemetry CLAUDE.md scanned grade B with 2 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 2mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- **Codex CLI** OTEL is configured via `~/.codex/config.toml` `[otel]` section (set by install.sh). Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **OTEL Collector image** (`otel/opentelemetry-collector-contrib`) is distroless: no shell, wget, or curl. Healthcheck is disabled in compose; use `./status.sh` (external curl) instead. How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
llm-cli-telemetry
Project Overview
Telemetry collection stack for Claude Code, Codex CLI, and Gemini CLI via shell function wrappers. Supports two modes: local (Docker Compose stack with Prometheus/Loki/Tempo/Grafana) and remote (direct OTLP export to any endpoint, no Docker required). Data flows through OTEL Collector or directly to remote endpoints.
Architecture
- Shell functions wrap
claude/codex/geminicommands, injecting OTEL env vars transparently telemetry.yamldrives all configuration;scripts/generate.shproduces collector config and compose overrides (local mode only)- Data collection: automatic OTEL export + optional local log file ingestion via filelog receiver
- Env var prefix:
LLM_CLI_TELEMETRY_* .setup-modefile stores current mode/protocol/endpoint/headers (pipe-delimited)
Key Files
| File | Purpose |
|---|---|
setup.sh |
Entry point: interactive setup (calls scripts/install.sh) |
start.sh |
Start local Docker stack with auto-generate |
stop.sh |
Stop Docker services (--clean for volumes) |
status.sh |
Mode-aware health check |
uninstall.sh |
Entry point: remove integration (calls scripts/uninstall.sh) |
scripts/lib.sh |
Shared utilities: logging, .setup-mode readers, common variables |
scripts/shell-integration.sh |
Shell functions (claude/codex/gemini) with OTEL env vars |
scripts/install.sh |
Interactive setup: mode selection, prerequisites, CLI configs |
scripts/uninstall.sh |
Remove shell integration, restore configs from .bak |
scripts/generate.sh |
telemetry.yaml -> collector-config.yaml + docker-compose.override.yml |
.env.example |
Environment variables template (Grafana creds, OTEL endpoint) |
.setup-mode |
Generated: setup state (mode|protocol|endpoint|headers) |
telemetry.example.yaml |
User config template (copied to telemetry.yaml on install) |
otel-collector/collector-config.yaml |
Generated OTEL Collector pipeline config |
docker-compose.yml |
Service definitions (collector, prometheus, loki, tempo, grafana) |
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.
- 2mo ago First seen · 91 lines · 1,192 tokens per session scan B ac35013f0578
llm-cli-telemetry CLAUDE.md is an instructions file published in the GitHub repository Mizune/llm-cli-telemetry (3 stars, last pushed 6mo ago), licensed MIT. It adds 1,192 tokens to every session, about $0.0048 per session on Opus 5.5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.