PluginBench
Skill
Fail
Audit score 45

ctx-stats

mksglu/context-mode

Display token savings and context window efficiency from context-mode this session.

What is ctx-stats?

Shows how much context window space context-mode saved during your current session, including token consumption, savings ratio, and per-tool breakdown. Use this to understand the efficiency gains from context compression.

  • Display total tokens consumed in the session
  • Show context savings ratio and percentage of data kept in sandbox
  • Provide per-tool breakdown of context usage
  • Read-only view—no modification of stats or knowledge base
  • Highlight key savings metric in a single summary sentence

How to install ctx-stats

npx skills add https://github.com/mksglu/context-mode --skill ctx-stats
Claude Code
Cursor
Windsurf
Cline

How to use ctx-stats

  1. 1.Invoke the skill with `/context-mode:ctx-stats`
  2. 2.The tool will return full tables with token consumption and savings data
  3. 3.Review the complete output including per-tool breakdown
  4. 4.Note the key savings metric highlighted in the summary sentence

Use cases

Good for
  • Check how much context window space you've saved with context-mode compression
  • Understand which tools are consuming the most context
  • Verify context-mode is working effectively for your workflow
  • Monitor session efficiency before context window limits are reached
  • Compare context savings across different sessions or tool combinations
Who it's for
  • Developers using context-mode for token optimization
  • AI coding agents managing limited context windows
  • Teams tracking context efficiency metrics
  • Anyone optimizing prompt engineering for cost or performance

ctx-stats FAQ

Can I reset or clear the stats?

No, ctx-stats is read-only. To permanently delete the indexed knowledge base, use ctx_purge instead.

What does the savings ratio tell me?

It shows how much of your original data stayed in the sandbox versus being expanded, expressed as a multiplier (e.g., 12.4x means context-mode compressed data by that factor).

Why should I check context stats?

Monitoring stats helps you understand whether context-mode is effectively saving tokens for your use case and when you might be approaching context window limits.

Does this tool modify my knowledge base?

No, ctx-stats only displays information. It does not change, reset, or delete any indexed content.

What if there's no data yet?

If you haven't used context-mode calls yet in the session, the tool will indicate 'No context-mode calls yet this session.'

Full instructions (SKILL.md)

Source of truth, from mksglu/context-mode.


name: ctx-stats description: | Show how much context window context-mode saved this session. Displays token consumption, context savings ratio, and per-tool breakdown. Read-only — shows stats only, no reset capability. To wipe the knowledge base entirely, use ctx_purge instead. Trigger: /context-mode:ctx-stats user-invocable: true

Context Mode Stats

Show context savings for the current session.

Instructions

  1. Call the mcp__context-mode__ctx_stats MCP tool (no parameters needed).
  2. CRITICAL: You MUST copy-paste the ENTIRE tool output as markdown text directly into your response message. Do NOT summarize, do NOT collapse, do NOT paraphrase. The user must see the full tables without pressing ctrl+o. Copy every line exactly as returned by the tool.
  3. After the full output, add ONE sentence highlighting the key savings metric, e.g.:
    • "context-mode saved 12.4x — 92% of data stayed in sandbox."
    • If no data yet: "No context-mode calls yet this session."

Purge

  • ctx_purge(confirm: true) — Permanently deletes all indexed content from the knowledge base. Use /context-mode:ctx-purge for this.