basemind-stats

basemind-stats is a skill for Claude Code from Goldziher/basemind. It costs 85 tokens per session (595 once invoked), scanned A, original, MIT.

A session dashboard for basemind that reports how many code-map searches ran, which operations were used, and an estimate of tokens saved compared with basic text searching and file reading.

In plain words
What is it for?
Use it when you want a usage summary for today or another supported time period, including recent operations and the assumptions behind the savings estimate.
Why use it?
It makes basemind usage visible instead of leaving activity and estimated savings unknown.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the basemind plugin — 15 skills, 10 commands, 6 agents, 2 hooks, 1 MCP server shipped together

Good fit Use it when you want a usage summary for today or another…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/goldziher/basemind/basemind-stats
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.

Any agent
npx skills add Goldziher/basemind --skill basemind-stats
Clone the repo
git clone --depth 1 https://github.com/Goldziher/basemind

Made for: Claude Code.

Or install basemind, the plugin that ships this one along with the rest of its 15 skills, 10 commands, 6 agents, 2 hooks, 1 MCP server.

Wrote 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.

agentmods badge for basemind-stats

README.md
[![agentmods](https://agentmods.dev/badge/skills/goldziher/basemind/basemind-stats.svg)](https://agentmods.dev/skills/goldziher/basemind/basemind-stats)
Your own site
<a href="https://agentmods.dev/skills/goldziher/basemind/basemind-stats"><img src="https://agentmods.dev/badge/skills/goldziher/basemind/basemind-stats.svg" alt="Measured on agentmods" height="20"></a>
Per session 85 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 595 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00085 $0.00595
Opus 5 $0.00043 $0.00298
Sonnet 5 $0.00017 $0.00119
Haiku 4.5 $0.00009 $0.00060

Measured 7d ago against content hash 922d1f49aa5b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

basemind-stats 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 7d 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.

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.

.codex-plugin/skills/basemind-stats/SKILL.md · 57 lines

What it actually says

basemind-stats — on-demand usage dashboard

Call admin mode telemetry and render the result as a markdown report.

When to use

The user asks "what has basemind done?", "how much is basemind helping?", "show me basemind stats", or invokes /bm-stats directly. This skill is strictly user-invoked — see Notes.

How to run

  1. Call admin { "mode": "telemetry", "window": "today" } (the default). If the user asks for a specific range, map it to one of "today", "1h", "24h", "all".

  2. Render a markdown block in this shape:

    ## basemind activity (today)
    - **N tool calls** ; top operations: code:outline (18), code:symbols (12), …
    - **~K tokens saved** vs grep + Read baseline
    - recent: code:outline (4ms, 312B), code:symbols (2ms, 180B), …
    
  3. If total_calls is 0, say so plainly ("no basemind activity in the window yet"). Don't pretend to have data.

  4. 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_baseline column on each row.

    The exact wording can vary; the principle (it's an estimate, here's why) cannot.

When the user asks "--explain"

If they invoke /bm-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.

Notes

  • Don't auto-display the dashboard at the start of every conversation. This skill is strictly user-invoked.
  • Don't pad missing data. If recent is empty, say so; don't invent example rows.
  • Don't claim a token-savings number without the disclosure sentence.
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. 7d ago First seen · 57 lines · 85 tokens per session scan A 922d1f49aa5b

Subscribe to this mod's changes

basemind-stats is a skill published in the GitHub repository Goldziher/basemind (98 stars, last pushed 5d ago), licensed MIT. It adds 85 tokens to every session and 595 once invoked, about $0.0004 per session on Opus 5. 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.

Related

Other skills, from other repositories

projectatlas

Use ProjectAtlas as the atlas-first orientation layer before broad source reads, with MCP-first task startup, short-alias worktree registration and routing, safe targeted initialization, ranked navigation, exact or federated graph evidence, purpose curation, health, lint, and repository-wide token reporting.

styler-ai/ProjectAtlas · 60 tokens

codex-coding-plugin

Build, review, or fix ProjectAtlas plugin/runtime installer integration for Codex, Claude Code, and OpenCode, especially version convergence, stale ProjectAtlas cache repair, MCP config generation, skill artifacts, host smoke tests, and fake-host tests for ProjectAtlas releases.

styler-ai/ProjectAtlas · 59 tokens

research

Performs deep research on a topic via deepresearch. Simulates a multi-step research process and returns a comprehensive research result as a string.

study8677/repobrain · 32 tokens

lsp-refactor

End-to-end safe refactor workflow — blast-radius analysis, speculative preview, apply to disk, verify build, run affected tests. Inlines lsp-impact + lsp-safe-edit + lsp-verify + lsp-test-correlation into one coordinated sequence.

blackwell-systems/agent-lsp · 57 tokens

trace-mcp-refactoring

Safe refactoring workflow using trace-mcp — assess risk, find candidates, check impact, and rename symbols across all files without missing import sites or cross-file references.

nikolai-vysotskyi/trace-mcp · 39 tokens

lsp-explore

Tell me about this symbol": hover + implementations + call hierarchy + references in one pass — for navigating unfamiliar code.

blackwell-systems/agent-lsp · 0 tokens