[FEATURE] /context: minimum-token display threshold to hide negligible entries (0-token MCP tools, <20-token skills)
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
/context lists every individual item in each category (MCP tools, skills, custom agents, etc.) regardless of how small its contribution is. In practice many entries report 0 tokens or < 20 tokens, and with dozens/hundreds of MCP tools and skills installed, these negligible entries dominate the output and bury the categories that actually matter for understanding context usage.
Proposed Solution
Add a minimum-token display threshold for /context output.
Items below the threshold are omitted from the listing (rolled into a summary line,
e.g. "+42 items under threshold, ~180 tokens total", rather than silently vanishing).
Suggested interface: a numeric threshold argument/setting, e.g.
/context --min-tokens=20 or context.minTokensDisplay: 20 in settings.json,
where: 0 (default) = show everything, current behavior.
1 = hide zero-cost (0 token) items only.
Alternative Solutions
Simpler fixed behavior — always collapse/hide exact 0 token entries (most common in mcp__* tools), leaving the < 20 tokens tier visible.
Priority
Critical - Blocking my work
Feature Category
CLI commands and flags
Use Case Example
A user with many MCP servers and plugin skills runs /context and gets a dozens-of-lines-long output dominated by 0-token/near-zero entries (e.g. mcp__code_generation__add_line_number: 0 tokens, amd-gfx-hw:review-cross-doc-consistency: < 20 tokens), obscuring categories that matter (system prompt, memory files, large skills). A threshold flag lets them scope the report to what's worth reviewing.
Additional Context
_No response_