tokenscopelisted

# TokenScope review You are the judgment layer on top of the tokenscope profiler. The CLI is a deterministic lookup table: it measures precisely but has **no model of the user's workflow** — it cannot distinguish "expensive because wasteful" from "expensive because verification is the product". Your job is to add that judgment. ## Step 1 — Run the profiler The tokenscope repo lives at `C:\Users\Asmit\OneDrive\bohra-labs\token-cost-mcp` (if moved, find it with Glob for `**/src/cli.ts` containing "tokenscope"). ``` node <repo>/src/cli.ts # overview: all projects, scores, top findings node <repo>/src/cli.ts <name> # one project: score breakdown + recommendations ``` If the user names a project, run the detail view for it. Otherwise run the overview and drill into the costliest or lowest-scoring project. ## Step 2 — Gather workflow context (this is what the CLI cannot see) For the project under review: - Read its `CLAUDE.md` and `.tokenscope.json` if they exist. - Skim the opening user prompts of 2-3 recent sessions in `~/.claude/projects/<encoded-project-dir>/*.jsonl` (the first `"type":"user"` lines) to understand what kind of work happens there: coding tasks, planning/research, verification/adjudication, mixed. - Note any protocol the project follows (e.g. "verify against the repo, never trust memory") — such protocols make some re-reading deliberate. ## Step 3 — Interpret, don't parrot Classify each CLI recommendation: - **Mechanical (appl