Claude Code Mods: the 3 mods to install first, without writing any code

You handle prospecting. List 30 [REAL ESTATE AGENCIES IN DALLAS] that [HAVE NO ONLINE APPOINTMENT BOOKING].
For each one: name, website, public email, and the specific reason [MY OFFER] matters to them.
Save everything to prospects.csv.
When you're done, tell @writer how many prospects you found.

You write the outreach emails. As soon as @prospector tells you prospects.csv is ready, read it.
Write one short, personal email per prospect, one file per email, in a drafts/ folder.
Don't send anything.
When everything is written, tell @manager how many drafts are ready.

You manage this team: @prospector finds the prospects, @writer writes the emails.
When I ask for an update, ask each of them for one line, then sum it up in three lines: done, blocked, next step.

Make a mod called team-room.
1. A /team command that opens a panel titled "Team". It shows every message this session sends to my other sessions or receives from them: the time, who, the first line. Newest on top.
2. A /standup command that asks @prospector and @writer, in one line, what they finished and what they're doing next. Each reply appears in the panel as soon as it arrives.
3. Keep the panel's history when the mod reloads.
Write it for my version of Claude Code, then run claude plugin validate and fix whatever comes up.

Make a mod called saver that sends my simple requests to the cheapest model.
1. On each prompt, classify the request. Simple: fixing a typo, renaming, formatting, a short summary, a quick question. Complex: a plan, debugging, new code, several steps. When in doubt, it's complex.
2. For a simple request, send every request in that turn to the model claude-haiku-5-5, except subagents' requests, and only if my prompt is under 100,000 tokens. Everything else stays on my current model.
3. Above the prompt, show one line: the last model used, and an estimate of what I saved today, based on each request's tokens and list prices (Haiku 5.5: $0.10 input, $0.50 output, per million).
4. Add /saver on and /saver off.
Write it for my version of Claude Code, then run claude plugin validate and fix whatever comes up.

Make a mod called dashboard.
1. A /hq command that opens a panel with three tabs:
- To do: a field to add a task, a button to tick off each task, a progress chart. The list carries over between sessions.
- To answer: emails from the last 24 hours I haven't replied to, read from my Gmail connector. One row per email: who, subject, how long ago. If there's no Gmail connector, say so in one line.
- Limits: my 5-hour and weekly usage limits, as two bars.
2. Above the prompt, a single line, for example: 3 to do · 2 to answer · 40% of my 5-hour limit.
3. Refresh the To answer tab every 10 minutes.
Write it for my version of Claude Code, then run claude plugin validate and fix whatever comes up.

git clone https://github.com/anthropics/claude-code-playground
claude --plugin-dir claude-code-playground/claude-code/mods/blast-radius

Make a mod that shows my git branch above the prompt.

Make a mod that shows, above the prompt, how much context I have left, in red below 20%.

Make a mod that holds any git push to main and asks me to confirm with two buttons: proceed or cancel.

Make a mod that adds a /wrapup command: three lines on what was done in this session, written by Haiku 5.5 and appended to wrapup.md.

Copy every mod written in this session into ~/mods.
Turn ~/mods into a local marketplace called my-mods, and install each mod from it so it loads in all my sessions.
Then show me /plugin.