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.
npx skills add mardab96/b2b-lead-generation-claude-skills --skill write-the-follow-upgit clone --depth 1 https://github.com/mardab96/b2b-lead-generation-claude-skillsWrote 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.
[](https://agentmods.dev/skills/mardab96/b2b-lead-generation-claude-skills/write-the-follow-up)<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.
<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>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00054 | $0.00920 |
| Opus 5 | $0.00027 | $0.00460 |
| Sonnet 5 | $0.00011 | $0.00184 |
| Haiku 4.5 | $0.00005 | $0.00092 |
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 12d 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.
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
- 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.
- Establish what you are actually asking for. One thing. A meeting, an answer, an introduction, or permission to close the file.
- 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.
- Mirror their register. If their emails are four words and no greeting, a three-paragraph message reads as a mismatch and slows the reply.
- Write it, then cut the first sentence. It is almost always throat-clearing, and the second sentence is usually the real opening.
- 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.
- 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.
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.
- 12d ago First seen · 80 lines · 54 tokens per session scan A 205cfb54485d
write-the-follow-up is a skill published in the GitHub repository mardab96/b2b-lead-generation-claude-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 920 once invoked, about $0.0003 per session on Opus 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…