From context-hogs
Show this repo's context-cost leaderboard — the files that pulled the most tokens into context
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-hogsGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.