Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From basemind
Renders an on-demand dashboard of basemind activity showing tool call counts, per-tool histogram, and estimated tokens saved vs a grep+Read baseline. User-invoked via `/basemind-stats`.
npx claudepluginhub goldziher/basemind --plugin basemindHow this skill is triggered — by the user, by Claude, or both
Slash command
/basemind:basemind-statsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Call the `telemetry_summary` MCP tool and render the result as a markdown report.
Opens a personal analytics dashboard in the browser showing Claude Code session activity, tool usage, error rates, parallel work patterns, and project focus. First run installs dependencies.
Generates usage analytics dashboard from Claude Code sessions with epistemic protocol coverage metrics, friction analysis, growth timelines, and improvement recommendations.
Displays real token usage and estimated savings for current Claude Code session from session logs—no AI estimation. Invoke via `/genshijin-stats` for session stats, `--all` lifetime totals, `--share` summaries, or `--since` periods.
Share bugs, ideas, or general feedback.
Call the telemetry_summary MCP tool and render the result as a markdown report.
Call telemetry_summary with { "window": "today" } (the default). If the
user asks for a specific range, map it to one of "today", "1h", "24h",
"all".
Render a markdown block in this shape:
## basemind activity (today)
- **N tool calls** ; top tools: outline (18), search_symbols (12), …
- **~K tokens saved** vs grep + Read baseline
- recent: outline (4ms, 312B), search_symbols (2ms, 180B), …
If total_calls is 0, say so plainly ("no basemind activity in the window yet").
Don't pretend to have data.
Always disclose the savings model. Add one sentence at the end:
Savings are heuristics. Tools with no realistic baseline (memory, document search, git wrappers) report 0 saved — see the
saved_baselinecolumn on each row.
The exact wording can vary; the principle (it's an estimate, here's why) cannot.
If they invoke /basemind-stats --explain or ask how the savings number is
derived, include the per-baseline breakdown from the per_baseline field of the
response and call out which tools fall into which bucket. The estimator lives in
src/mcp/savings.rs if they want to read the code.
recent is empty, say so; don't invent example rows.