By wangshunnn
Logs Claude Code hook events (tool usage, subagents, sessions) to a project-local telemetry file, then builds and opens a self-contained HTML dashboard in the browser to visualize per-turn knowledge-base hit rates.
Matches all tools
Hooks run on every tool call, not just specific ones
Executes bash commands
Hook triggers when Bash tool is used
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Modifies files
Hook triggers on file write and edit operations
Modifies files
Hook triggers on file write and edit operations
Runs pre-commands
Contains inline bash commands via ! syntax
Runs pre-commands
Contains inline bash commands via ! syntax
Offline telemetry and a self-contained dashboard for Claude Code and Codex. It helps you see which docs, rules, skills, and agent instructions are actually used in each turn.
/plugin market add wangshunnn/claude-telemetry
/plugin install claude-telemetry
/reload-plugins
After installation, telemetry starts collecting from new turns. Use Claude in your project for a few turns, then open the dashboard:
/claude-telemetry:open
This builds the current project's offline dashboard and opens it in your browser.
You can add .claude/telemetry/ to the instrumented project's .gitignore.
Use the explicit source:
/plugin install claude-telemetry@claude-telemetry
Update the Claude Code plugin:
/plugin market update claude-telemetry
/plugin update claude-telemetry
/reload-plugins
Use the npm package when you want project-local Codex hooks and a dashboard for Codex turns.
npm i -g @wangshunnn/claude-telemetry
cd /path/to/your/project
claude-telemetry install codex
Then use Codex in that trusted project for a few turns and open the Codex dashboard:
claude-telemetry open codex
Codex project hooks need both of these Codex-side prerequisites:
features.codex_hooks = true is enabled in your Codex config.For example, in ~/.codex/config.toml:
[features]
codex_hooks = true
Useful Codex commands:
claude-telemetry open # interactively choose Codex or Claude when both have data
claude-telemetry open codex # open Codex telemetry
claude-telemetry doctor codex # check hook setup, trust, config, PATH, and data
claude-telemetry uninstall codex
Codex telemetry is stored separately under .codex/telemetry/. Add it to the instrumented project's .gitignore:
.codex/telemetry/
.claude/telemetry/ for Claude Code and .codex/telemetry/ for Codexindex.html and snapshot.jsonCLAUDE_TELEMETRY_ROOT only if you explicitly want a shared telemetry directory outside the project.claude-telemetry CLI plus the Claude Code plugin files used by the marketplace install path.MIT — LICENSE
npx claudepluginhub wangshunnn/claude-telemetry --plugin claude-telemetryMulti-model consensus engine integrating OpenAI Codex CLI, Gemini CLI, and Claude CLI for collaborative code review and problem-solving.
Memory compression system for Claude Code - persist context across sessions
Editorial "Web Designer" bundle for Claude Code from Antigravity Awesome Skills.
Complete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, and rules evolved over 10+ months of intensive daily use
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses