From context-hogs
Shows a repository's context-cost leaderboard identifying files that consume the most tokens in Claude Code sessions, with advice for reducing overhead.
How this skill is triggered — by the user, by Claude, or both
Slash command
/context-hogs:leaderboardThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
!`node "${CLAUDE_SKILL_DIR}/../../context-hogs.js" --render 2>/dev/null || node "${CLAUDE_PLUGIN_ROOT}/context-hogs.js" --render`
!node "${CLAUDE_SKILL_DIR}/../../context-hogs.js" --render 2>/dev/null || node "${CLAUDE_PLUGIN_ROOT}/context-hogs.js" --render
The table above is this repository's most token-expensive files, aggregated across
your recent sessions (read count, cumulative tokens, estimated cost). It is produced
by the context-hogs hook, which records as you work.
Briefly call out the top 1–3 offenders and suggest one concrete fix each — for
example: split an oversized file, exclude a generated/vendored path, or add the
suggested CLAUDE.md / permissions.deny block for a file Claude keeps re-reading.
Keep it short; do not re-run any commands.
npx claudepluginhub karanb192/claude-code-hooks --plugin context-hogsDisplays token economics dashboard showing savings from search-first (turbo-search) vs blind file reading. Analyzes session activity logs and codebase stats via /token-stats.
Ranks files by relevance to the user's task — based on git state, mentioned paths, and historical patterns — with token-budget-aware offset/limit suggestions.
Tracks tokens, analyzes caching behavior, identifies bottlenecks in tool usage, and estimates costs to optimize Claude Code session performance and efficiency.