Mod ideas from your last 20 sessions
Requests you repeat, commands you stop or undo, how you check changes: ranked by how much each would help, your words quoted.
340 saves on X, as of Posted
Prompt
Read this guide: https://claude.dev/blog/getting-started-with-claude-code-mods/
Then use it to go through my last 20 sessions (this project's .jsonl logs under ~/.claude/projects/) and see how I use you day to day. Find three kinds of things worth turning into a mod:
1. Things I keep asking you, or asking you to do. Each mod in the guide answers one question, like how full the context is. Pick out the questions and requests I repeat across sessions, with counts and my exact words, then decide whether each fits a readout above the prompt, a pane beside the conversation, or a /command.
2. Commands that make me nervous: ones I stopped partway, rejected, or had you undo afterwards.
3. How I check your changes: asking you to list the files you changed, paste the diff, or explain a change.
For each idea, give it a name, quote my words, and write a few 'What it should show' lines in the style of the guide's token-weather prompt. If a status line or a setting can already do it, say so, and don't force it into a mod. Rank the ideas by how much they'd help me, and tell me how to keep a mod around once it's built.
Show me the ideas first. Don't build anything until I pick.Next Send it to Opus 5.5 in Claude Code, in a project you use a lot.
Have Opus 5.5 go through your last 20 Claude Code sessions, and it can tell you which mod you most need to build for yourself.
A mod is a small feature you add to Claude Code yourself, and you don’t need to write any code. Describe what you want to see and Claude writes it in one turn. For example, showing how full your context is, or which files it just changed, right on your screen.
Share this tip
