Anthropic just published its 𝗳𝘂𝗹𝗹 𝗴𝗲𝘁𝘁𝗶𝗻𝗴-𝘀𝘁𝗮𝗿𝘁𝗲𝗱 𝗴𝘂𝗶𝗱𝗲 for Claude Code mods. You can ask Opus 5.5 to use it to go through your past sessions and find the mods you most need to build for yourself.

A mod is a small feature you add to Claude Code. The guide's three mods take the things you'd normally stop to ask it and 𝗽𝘂𝘁 𝘁𝗵𝗲𝗺 𝗿𝗶𝗴𝗵𝘁 𝗼𝗻 𝘀𝗰𝗿𝗲𝗲𝗻: how full the context is, what this command is about to delete, and what it just changed. You just describe what you want to see, and Opus 5.5 writes the code. So don't rush to copy the examples. Start with the things you keep stopping to ask about.

Send this prompt to Opus 5.5 👇

"Read this guide: claude.dev/blog/getting-started-with-cl…

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."