Skip to content
← All guides

Claude Duet Early Access + The 7 Best Claude Mods

Here's the Duet link I promised, right at the top. Below it are the 7 best Claude mods, what each one does, and the exact prompts to get them running. No coding.

Zach Oct 2026 · 5 prompts

Claude Duet: get early access

Join the Claude Duet waitlist →

Claude Duet is the one you hand a job, close the app, and it keeps working. It runs on its own computer in the cloud, sends you a morning brief, and only pings you when something actually needs you.

What a mod is

A mod is a small add-on that changes how Claude Code looks and works. It can add a meter above your prompt, stop a risky command before it runs, or open its own panel beside the chat.

You don't have to write any code. You describe the mod in plain English and Claude builds it, then it shows up when Claude finishes.

  • Where they run The Code tab in the Claude desktop app, or Claude Code in a terminal
  • Version Claude Code 2.1.287 or later
  • Coding needed None

To try any prompt below, open the Claude desktop app, click the Code tab, pick a project folder, and paste it in. If Claude asks to turn on hot reload, allow it. That's what makes the mod appear without a restart.

Install the 3 official mods

Anthropic built these and shares the code. One prompt installs all three.

  • 1. Token Weather
    A live forecast of how full your chat is, right above your prompt. It goes from Clear to Cloudy, Showers, Storm and then Compact soon, so you always know when Claude is about to run low on context.
  • 2. Blast Radius
    Claude tries to run something like rm -rf, git reset --hard or a force push, and this holds it first. You see exactly what it would change, with Proceed and Cancel buttons.
  • 3. Replay Theater
    Steps through every edit Claude made in the last turn, one change at a time. Type /replay or press r.
Prompt 1: Install all 3 official mods 
Install Anthropic's 3 official sample mods for me: Token Weather, Blast Radius and Replay Theater.

1. Run claude --version. Mods need 2.1.287 or later. If mine is older, update Claude Code first and tell me.
2. Clone the repo into my home folder:
   git clone https://github.com/anthropics/claude-code-playground.git ~/claude-code-playground
3. Go to ~/claude-code-playground/claude-code/mods and add that folder as a local marketplace:
   claude plugin marketplace add ./
4. Install all 3 for every project:
   claude plugin install token-weather@claude-code-playground-mods --scope user
   claude plugin install blast-radius@claude-code-playground-mods --scope user
   claude plugin install replay-theater@claude-code-playground-mods --scope user

When you're done, tell me in plain English what each one does, how I'll know it's working, and whether I need to start a new session to see them.

Build these 4 by describing them

People are already sharing their own versions of these ideas. You don't need to go find them. Paste the prompt and Claude builds yours. Then keep asking for changes until it's exactly how you want it.

4. Chat Bridge: two chats that talk to each other

One chat plans and the other builds, and they pass the work back and forth so you're not copying between them.

Prompt 2: Chat Bridge 
Make me a Claude Code mod called chat-bridge, so two of my Claude Code chats can talk to each other. One does the planning, the other does the building.

What it should do:
- Add a slash command, /bridge [name], that names this chat (for example /bridge planner or /bridge builder).
- Give Claude a tool that sends a message to another named chat, and a way to read messages sent to this one. Keep the messages in a shared folder on my computer so any chat can reach them.
- Draw one line above the prompt showing this chat's name and how many unread messages it has.
- Only pass messages along. It should never run anything from another chat without showing it to me first.

When it's built, tell me exactly what to type in each chat to try it: one chat plans a small landing page and sends the plan, the other picks it up and builds it.

5. File Map: see what Claude is touching

A live list of every file Claude has read or changed, so you can see what it's doing without opening anything else.

Prompt 3: File Map 
Make me a Claude Code mod called file-map: a live list of what Claude is working on, in a pane beside the chat.

What it should show:
- Every file Claude has read or edited this session, newest first.
- A marker for whether each file was read or edited, plus how many times.
- A slash command, /files, that opens and closes the pane.

It should only watch and draw. It should never block or change what Claude does.

6. Agent Watch: see what your subagents are doing

When Claude hands work to subagents, the chat can go quiet while a lot happens underneath. This shows you who's doing what.

Prompt 4: Agent Watch 
Make me a Claude Code mod called agent-watch: a live panel of every subagent Claude has running.

What it should show, one row per subagent:
- What it's working on, in a few words.
- The tool it's using right now.
- How long it's been running, and whether it's working, done or failed.
- A slash command, /agents, that opens and closes the panel.

It should only watch and draw. It should never start, stop or change an agent.

7. Remember This: stop repeating yourself

Turns the correction you keep making into a saved instruction, so you only ever have to say it once.

Prompt 5: Remember This 
Make me a Claude Code mod called remember-this, so I stop correcting Claude about the same thing over and over.

What it should do:
- When I start a message with "remember:", or correct Claude the same way twice in a session, turn that into one short proposed instruction.
- Show me the proposed instruction in a pane with three buttons: Save, Edit and Skip.
- Save adds it to the CLAUDE.md file in my project, so every future session follows it.
- Never save anything without me pressing Save.

When it's built, tell me one thing to type so I can test it.

Make your own

Every mod starts with one annoyance. Ask yourself what you keep checking, what makes you nervous, or what you wish you could see. Then write the prompt the same way as the ones above:

  1. Name it and say what it's for. "Make me a Claude Code mod called cost-meter that shows what this session has used."
  2. Say what you want to see. Where it goes and what's in it. You don't need to know how it works.
  3. Say what it should never do. "It should only watch and draw" keeps it from getting in your way.
  4. Keep asking for tweaks. "Make it red at 70%" or "add the cost at the end." It updates as you go.

Want to browse instead? Mods install like any plugin, so check the Claude directory or type /plugin in Claude Code. For the details, read Anthropic's getting started guide and the mods docs.