session-scan

# Session Scan (Tier 1) Compute deterministic metrics for sessions discovered via ccrider MCP. ## STOP — Read Before Executing **NEVER call `mcp__ccrider__get_session_messages` in main context.** Each response is 5-50KB of JSON. Fetching N sessions directly = context crash. **You MUST delegate all scoring to subagents.** The main context only does: discovery, deduplication, subagent spawning, and result collection. ## Requirements Requires **ccrider MCP**. If not available: > ccrider MCP is required. See: <https://github.com/neilberkman/ccrider> ## Usage ``` /session-scan # Last 7 days, up to 50 sessions /session-scan --since 2026-02-01 # Since specific date /session-scan --project enaia # Filter by project name /session-scan --limit 20 # Cap session count /session-scan --list # Discovery only, no scoring /session-scan --rescan # Recompute already-scanned sessions ``` ## What Main Context Does ### 1. Parse Arguments Extract from `$ARGUMENTS`: - **`--since DATE`**: ISO date filter (default: 7 days ago) - **`--project NAME`**: Filter by project path substring - **`--limit N`**: Max sessions to process (default: 50) - **`--list`**: Discovery only — show table, skip scoring - **`--rescan`**: Recompute metrics for already-scanned sessions ### 2. Discover Sessions (safe — response is ~1KB) ``` mcp__ccrider__list_recent_sessions(limit: N, project: PROJECT, after_date: SINCE) ``` Filter ...