Packlight — Development skill for Claude Code

packlight

See what your coding agent carries, keep what you use, archive the rest.

Claude Code loads every skill, agent, hook and MCP server you have installed into every session, used or not. packlight scans your setup and your local session logs, then writes one self-contained report. The report shows:

• how many tokens each session starts with, by source: MCP tool names, the skill listing, hook text, agent descriptions
• which skills are pushed out of Claude Code's skill listing
• how much text each hook injects
• which items were not used in any session since they were installed

Works with **Claude Code** and **Codex**. packlight picks Claude Code when `~/.claude` exists; for Codex, add `--agent codex` (`packlight --agent codex`, `packlight fix --agent codex`). Each tool gets its own report: `~/.packlight/report-claude-code.html` for Claude Code, `~/.packlight/report-codex.html` for Codex. For Codex the headline is measured: Codex logs the input tokens of each session's first request, and packlight reports the median. Codex plugins and MCP servers are switched off in `~/.codex/config.toml`, so packlight lists them with the exact line to change rather than editing that file.

**[See a sample report →](https://cooperism-lab.github.io/packlight/sample/)** (an invented setup, so you can click around before installing).

You mark what to archive. `packlight apply` moves it out reversibly, and `packlight restore` brings it back.

Everything runs locally: no telemetry, and no network calls from the CLI or the report.

Status

Issues 1 to 3 are built (v0.1 scope). `packlight` scans your setup and opens a report: what every session starts with (MCP tool names per server, the skill listing, MCP instructions, hook text), which skills Claude Code dropped from its