Menu
Build an optimal context pack for the user's task — ranked file list with offset/limit suggestions, based on git state, mentioned paths, and historical patterns
Configure token budget limits, auto-compact settings, and view current budget status (model-aware — supports Opus 4.7 1M context tier)
Analyze the user's last prompt for clarity, scope and specificity — give a quality score and concrete suggestions to make the next prompt produce better results
Health check for the context-optimizer plugin install — verifies versions, hooks, data dir, model config, and reports any issues
Calculate monthly token savings and ROI by model
Show recent session summaries for quick context recovery
Show ContextShield status and waste protection stats
| name | cco-pack |
| description | Build an optimal context pack for the user's task — ranked file list with offset/limit suggestions, based on git state, mentioned paths, and historical patterns |
| license | MIT |
| allowed-tools | ["Bash","Read"] |
When the user runs /cco-pack or asks "what files do I need for X", build a curated, token-budget-aware list of files to load instead of guessing or reading the whole repo.
node ${CLAUDE_PLUGIN_ROOT}/src/smart-pack.js "the task description"
Or for the current git state without a description:
node ${CLAUDE_PLUGIN_ROOT}/src/smart-pack.js
Or to feed it back into automation as JSON:
node ${CLAUDE_PLUGIN_ROOT}/src/smart-pack.js --json "..."
Priority order:
For each file the pack also suggests offset / limit — pointing at the structurally relevant section based on file landmarks (function/class declarations near task keywords).
Pack stops adding files once it would exceed 25% of the user's effective context budget. The budget itself respects the configured model (e.g. 1M for opus-4.7-1m).
After running, present the list to the user and offer to:
/cco-templates create <name>)