Audit Claude Code Context Usage

Review recent Claude Code transcripts and current session features to identify unused tools and estimate potential context-token savings.

Yevhenii Bilyk Republished on Nov 02 0 Bookmarks 0 Copies
Bookmark 0

Example outputs

Example result for Audit Claude Code Context Usage

Prompt template

Format
Text Parameterized
Inputs
lookback_period (text) · Optional · Default: 30 days ClaudeCodeTranscripts (document) · Required CurrentSessionToolsAndSkills (text) · Required
Outputs
UsageAuditAndRecommendations (text)
Go through my Claude Code transcripts in ~/.claude/projects/ from the last ${lookback-period:30 days} and count which tools, skills, MCP servers and features (Artifact, Workflow, Chrome, remote control, scheduling, AskUserQuestion and so on) I actually used, then compare that with the tools and skills loaded in this session and recommend what I can turn off in ~/.claude/settings.json without losing anything I rely on, with a rough token saving for each.

Replace the ${…} placeholders with your values before using this prompt. See parameters and defaults below

Parameters

Replace each placeholder with your own value, or use its default when one is provided

${lookback-period:30 days} lookback-period Default: 30 days

What you'll create

The review counts actual feature use over a chosen lookback period. Suggested settings removals prioritize preserving relied-on capabilities while estimating token savings.

Frequently asked questions

What lookback period is provided by default?

Thirty days.

Does the goal allow removing needed tools?

No. The brief prioritizes keeping relied-on capabilities.

Comments

Tried this prompt? Share what you made, compare results, or ask a question

Up to 4 results. Images up to 2 MB; MP4, WebM, or MOV videos up to 4 MB each