1. What Claude Code Mods Do
▶ 0:00Claude Code just shipped mods: if there is something you wish the Claude Desktop app did, you can ask it to do it, and it will change. You can customize the UI, swap in your own features, and toggle them on and off. The official release post showed off a few examples — Token Weather (how full the context is, in the UI), Blast Radius (what a command would delete before it deletes it), and Replay Theater (step-by-step replay of the edits and diffs that just happened).
Under the hood, mods are plugins — a little bit of code installed with /plugin in the CLI or desktop app — and you create them with plain English. The rest of the video is a tour of the five mods Nate actually runs, each one born from a specific friction point in his own workflow.
2. Next Steps
▶ 0:35The first mod comes from Thoric, one of the engineers at Claude Code. At the end of every turn it pops up a small UI element with three recommendations for what to do next — or you dismiss it. Ask "what action items do I have for ClickUp today?" and the mod returns concrete next steps: close the demo and hackathon tasks, push the certification due dates to next week, run the morning coffee briefing.
Its real value shows when you are building: instead of steering your own day, the mod suggests "fix this bug first, then merge these changes" — a persistent nudge that keeps an app or automation moving forward. Setup is a copy-paste: give the snippet to Claude and say "set up this mod," and it appears in that same chat in about thirty seconds.
3. Building Mods in Natural Language
▶ 1:55Mods ship inside plugins and are installed with /plugin; you create one by opening Claude, updating it, and saying "I want to make a mod for this." Nate's own process: he asked Claude to read through his session logs, understand how he uses Claude Code, and find the top five mods that would save money, move faster, and stay organized — then he built the ones that were genuinely useful and skipped the viral-but-useless visual gimmicks.
The management model is lightweight: mods live in local files, turn on and off with slash commands, and are built the same way every time — say "build me a mod for X," then ask "how do I turn it on, how do I turn it off?" The pattern applies to any of the mods in this list.
4. Cache Keeper
▶ 2:53The second mod is about not wasting money. Everything in a chat is cached, so new messages are not re-read at full cost — but the cache expires after roughly 60 minutes of inactivity, after which you repay for all that text. Cache Keeper surfaces what matters at a glance: the cache timer (57 minutes, then back to 60), the context size (109,000 tokens), the session, 5-hour, and weekly limits, and what the session would have cost under API billing.
Two extras make it genuinely useful. A button runs the session handoff — his skill for moving to a fresh context before "context rot" sets in — turning a manual copy-clear-paste sequence into one or two clicks. And when the cache is about to go cold, it fires a notification: "reprompt this, or run a compact or handoff?" — so you save the cache instead of silently paying for it again.
5. Recording Mode
▶ 5:30For anyone who records their screen: a recording mode that blurs sensitive details. Ask Claude for the email on your GitHub account, and with recording mode on it keeps the real address off screen and shows placeholders instead. The same holds for financial figures or internal information that would otherwise leak into a video.
The subtle part is that Claude still reads the real values — it changed a price from $29 to $39 correctly while blurring the number on screen — it just redacts the display. The toggle is a slash command (record / record off), and because mods are plain text, you can flip it on for the duration of a recording session and off when done.
6. Goal Meter
▶ 7:23Nate runs a lot of /goal prompts, and the recurring problem is losing track of where a long-running goal actually is. Goal Meter adds a small UI to any /goal: the prompt, the current phase ("planning," "waiting for Claude's task plan"), elapsed time, and a task list that checks off as the agent works — with a percentage-complete view.
For a goal that produced four tasks (fetch comment tooling, pull comments from the last ten videos, analyze for common themes, report the most important theme), the meter shows each step flipping to done in real time. Click through to see all tasks, and it also lists other chats and goals — so if you are running twelve sessions in parallel, every goal is visible in one spot instead of scattered across tabs.
7. Collision Guard
▶ 9:11The last mod protects against a classic multi-agent footgun: before every edit, write, or notebook edit, it checks whether the file was touched in the last 30 minutes — and if it was, it asks what to do. Change a price in one chat, open another chat and say "add a most-popular badge to the pro plan," and the mod stops: "another open chat edited the file just now — do you want to edit it here too?"
The options are proceed, move to a worktree, cancel, or type something else. It is deliberately different from a hook: it is not a pre-tool-use block, and it does not act automatically — it recognizes a potential conflict and surfaces the question in the UI. You could approximate this with a skill or in CLAUDE.md, but as a mod it is quick to build and means you never silently overwrite a file another agent is working on.
Key Takeaways
- Mods are plugins you write in plain English — say "build me a mod for X," install with
/plugin, toggle with slash commands. - Next Steps turns the end of every turn into three recommended actions, keeping a build moving without you steering it.
- Cache Keeper puts context size, session limits, and API cost in the UI — and warns before the ~60-minute cache goes cold so you hand off or reprompt instead of repaying.
- Recording Mode blurs emails and financial figures on screen while Claude still reads the real values underneath.
- Goal Meter makes long
/goalruns legible — phase, elapsed time, and a task list with progress — across parallel sessions. - Collision Guard flags any file another chat touched in the last 30 minutes before you write to it, then asks how to proceed.
- The through-line: mods turn one-off habits and terminal status lines into persistent UI affordances — customizing the app, not just the prompts.