You commented MODS. Here are all ten prompts, word for word. Paste one into Claude Code and it builds the mod for you. No code from you.

How to use these

  1. Open Claude Code v2.1.287 or later. Check with claude --version.

  2. Paste a prompt. Claude writes the mod, installs it and hot reloads it.

  3. Check it loaded with /plugin.

A mod can draw a pane, a band or a status line, redraw Claude Code's UI, send one request to a different model, or message another of your sessions. Anthropic shipped them on 1 October 2026.

The three from the reel, word for word

Mod 1: see everything you're running

Build me a side pane that shows me everything that I'm running.

Mod 2: make two sessions talk

Let this session message another session.

Mod 3: cheap model for simple tasks

Send simple tasks to the cheapest model.

Pro versions: same three, better results

Same ideas, fuller wording. These get a better first build.

Mod 1, pro

Build me a mod: a side pane that shows every agent I'm running, what each one is doing right now, and when it finished.

Name what you want on the pane. It stops Claude guessing.

Mod 2, pro

Build me a mod that lets this session send a message to my other Claude Code session. I want one session planning and the other building, passing work between them.

Say who plans and who builds. Two sessions with roles beat two sessions chatting.

Mod 3, pro

Build me a mod that sends simple requests (renames, typo fixes, small edits) to a cheaper model, and keeps everything else on my main model. Show me in the transcript which model handled each request.

This is the one that saves your limit. Start strict: only route the obvious small stuff, and read the transcript lines for a day before you widen it.

Seven more you can use today

4. Context fuel gauge

Build me a mod: a band above the prompt that shows how full my context window is after each request, and turns red past 80%.

5. Tool-call counter

Build me a mod that counts the tool calls Claude makes this turn and shows the count beside the spinner.

6. Production guard

Build me a mod that holds any command touching production config or a .env file, and asks me to confirm before it runs.

7. Blast-radius check

Build me a mod that holds risky shell commands like rm -rf or git push --force, shows me what they'd change, and gives me Proceed and Cancel buttons.

8. CI status pane

Build me a mod: a pane beside the conversation that shows my latest GitHub Actions run for this repo, refreshing every minute.

9. Replay the last turn

Build me a mod that adds a /replay command, which steps through every file edit Claude made in the last turn, one at a time.

10. Usage meter

Build me a mod: a status line under the prompt that shows the tokens used this session and a running total for today.

Before you install anyone else's mod

Mods aren't sandboxed. A mod runs with your permissions, so it can read your files and secrets, see your prompts, approve tool calls and spend your usage. Mods you build from your own prompt are fine. For anyone else's, check what it does first:

claude plugin validate ./some-mod

That command lists the hooks and calls the mod makes. Read it before you install.

If a mod misbehaves, start Claude Code with --safe-mode. Every mod you installed stays off for that session. To see which mods are loaded, run /plugin.

Start with Mod 1. Run it for a day, then add the next. If one of these saves you an hour, reply and tell me which.

Mike

PS: I build lead-gen systems for local businesses at OptiMAX, optimax-ai.com.