agentmods.dev

write-the-follow-up

write-the-follow-up is a skill for Claude Code, Codex from mardab96/b2b-lead-generation-claude-skills. It costs 54 tokens per session (920 once invoked), scanned A, original, MIT.

A writing aid for composing the next email after a call, proposal, event or stalled conversation. It uses the actual discussion and agreed next steps rather than filling in a generic follow-up template.

In plain words
What is it for?
Use it to write follow-ups from the conversation thread, the recipient's priorities, ownership of the next step and any real deadline. For a thread silent for weeks, first investigate why it went quiet with a separate ghosted-after-the-demo review.
Why use it?
It helps when repeated rewrites produce messages with no new information for the recipient to respond to. It focuses the email on something useful that changed or was learned since the previous message.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 6repo 3mo ago A scan 54 tokens original MIT

Good fit Use it to write follow-ups from the conversation thread, the recipient's priorities, ownership of the next step and any real deadline. For a thread silent for weeks, first investigate why it went quiet with a separate ghosted-after-the-demo review.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mardab96/b2b-lead-generation-claude-skills/write-the-follow-up
View source ↗ mardab96/b2b-lead-generation-claude-skills
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add mardab96/b2b-lead-generation-claude-skills --skill write-the-follow-up
Clone the repo
git clone --depth 1 https://github.com/mardab96/b2b-lead-generation-claude-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for write-the-follow-up

README.md
[![agentmods](https://agentmods.dev/badge/skills/mardab96/b2b-lead-generation-claude-skills/write-the-follow-up/github.svg)](https://agentmods.dev/skills/mardab96/b2b-lead-generation-claude-skills/write-the-follow-up)
Your own site
<a href="https://agentmods.dev/skills/mardab96/b2b-lead-generation-claude-skills/write-the-follow-up"><img src="https://agentmods.dev/badge/skills/mardab96/b2b-lead-generation-claude-skills/write-the-follow-up/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for write-the-follow-up

Your own site · 80×15
<a href="https://agentmods.dev/skills/mardab96/b2b-lead-generation-claude-skills/write-the-follow-up"><img src="https://agentmods.dev/badge/skills/mardab96/b2b-lead-generation-claude-skills/write-the-follow-up.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 920 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.00920
Opus 5.5 $0.00022 $0.00368
Sonnet 5.5 $0.00011 $0.00184
Haiku 4.5 $0.00005 $0.00092

Measured 2mo ago against content hash 205cfb54485d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

write-the-follow-up scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

write-the-follow-up/SKILL.md · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Write the Follow-Up

Use this skill when

The next email has to go out and it has been rewritten three times already.

Follow-ups fail for a boring reason: they contain no new information. The recipient has nothing to react to, so reacting costs them effort with no return, so they do not. Everything below exists to give them something worth answering.

For a thread that has already gone silent for weeks, use ghosted-after-the-demo first to work out why, then come back here to write it.

Required input

  • What happened: the call, the proposal, the event, the last message.
  • The thread so far, if there is one.
  • Who you are writing to and what they can actually decide.

Useful:

  • what they said they cared about, in their words
  • what was agreed as the next step and who owned it
  • any deadline that is genuinely real
  • how formal their own messages are

Analysis workflow

  1. Find the new information. Something must have changed since the last message: an answer to their question, a relevant example, a piece of thinking they have not seen. If nothing has changed, that is the finding, and the honest options are to create something worth sending or to wait.
  2. Establish what you are actually asking for. One thing. A meeting, an answer, an introduction, or permission to close the file.
  3. Match the length to the stage. After a first call, short. After a proposal, short. Nobody has ever complained that a follow-up was too brief.
  4. Mirror their register. If their emails are four words and no greeting, a three-paragraph message reads as a mismatch and slows the reply.
  5. Write it, then cut the first sentence. It is almost always throat-clearing, and the second sentence is usually the real opening.
  6. Check the ask is answerable in one line. If replying requires them to think, schedule or consult someone, the reply rate drops by an order of magnitude.
  7. Offer the exit. A message that makes it easy to say no gets more replies than one that only permits yes, and a clear no is worth more than another week of silence.

Read the full file on GitHub · 80 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 80 lines · 54 tokens per session scan A 205cfb54485d

Subscribe to this mod's changes

write-the-follow-up is a skill published in the GitHub repository mardab96/b2b-lead-generation-claude-skills (6 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 920 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Marketing and SEOWriting and docs
Related

write-the-follow-up compared with skills from other repositories

write-the-follow-up next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
write-the-follow-upmardab96/b2b-lead-generation-claude-skillsSkill63mo agoMITA54Claude Code, Codex
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code