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 Salesably/salesably-marketplace --skill follow-up-emailsgit clone --depth 1 https://github.com/Salesably/salesably-marketplaceWrote 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/salesably/salesably-marketplace/follow-up-emails)<a href="https://agentmods.dev/skills/salesably/salesably-marketplace/follow-up-emails"><img src="https://agentmods.dev/badge/skills/salesably/salesably-marketplace/follow-up-emails/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/salesably/salesably-marketplace/follow-up-emails"><img src="https://agentmods.dev/badge/skills/salesably/salesably-marketplace/follow-up-emails.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.00042 | $0.01390 |
| Opus 5 | $0.00021 | $0.00695 |
| Sonnet 5 | $0.00008 | $0.00278 |
| Haiku 4.5 | $0.00004 | $0.00139 |
Grade A, and why
follow-up-emails 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Follow-Up Emails
This skill creates professional, well-structured follow-up emails that capture key discussion points, confirm action items, and maintain deal momentum after sales conversations.
Objective
Transform sales call insights into clear, compelling follow-up emails that reinforce value, confirm next steps, and keep deals moving forward.
Email Structure
1. Personalized Opening
Brief greeting that acknowledges the conversation.
Good Examples:
- "Thanks for making time to chat today."
- "Great connecting with you this afternoon."
- "Appreciated the candid conversation earlier."
Avoid:
- Generic "Hope this email finds you well"
- Overly effusive thanks
- Restating obvious facts ("As we discussed...")
2. Next Steps Section
The most important part-clear action items.
Format:
## Next Steps
**Your action items:**
- [Action 1] - by [date]
- [Action 2] - by [date]
**My action items:**
- [Action 1] - by [date]
- [Action 2] - by [date]
Guidelines:
- Lead with their action items (creates accountability)
- Be specific about what and when
- Keep it to 2-4 items total
- Make deadlines clear but reasonable
3. Discussion Summary
Organized recap of what was covered.
Sections to Include:
Challenges Discussed:
- Key pain points they mentioned
- Impact of those challenges
- Urgency or timeline drivers
Goals Identified:
- Desired outcomes they expressed
- Success criteria mentioned
- Priority areas
Solutions Discussed:
- How your solution addresses their needs
- Features or capabilities most relevant
- Differentiation from alternatives
4. Professional Closing
Brief sign-off with clear call to action.
Good Closings:
- "Looking forward to our follow-up on [date]."
- "Let me know if anything changes or if you have questions."
- "Happy to chat before then if anything comes up."
Customization Options
Tone Settings
Formal:
- Full sentences, proper grammar
- Professional language
- Structured format
- Appropriate for executives or first interactions
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 · 248 lines · 42 tokens per session scan A 5efde46f2f43
follow-up-emails is a skill published in the GitHub repository Salesably/salesably-marketplace (49 stars, last pushed 8mo ago), licensed MIT. It adds 42 tokens to every session and 1,390 once invoked, about $0.0002 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-30.
Other skills, from other repositories
gtm-brain-builder
Orchestrate the creation or maintenance of a source-backed GTM brain for a company, including tool connection, section routing, Grill-me questions, session relay, section-agent sequencing, and recurring freshness workflows. Use when a user wants to build a GTM Brain or make one shareable/useful for sales, marketing…
design-system-agent
Create a source-backed design-system brief and walk an operator through using Claude.ai/design or Codex design workflows to generate, review, export, and import a brand kit/design system into the GTM Brain.
grill-me
Always-on decision-quality skill for stress-testing GTM brain claims, positioning, ICP, proof, tone, campaign learnings, source interpretation, and strategy branches by asking one pointed operator question at a time with a recommended hypothesis.
brand-voice-agent
Build brand guidance and separate speaker-tone profiles for a GTM brain, keeping person-specific tone distinct from sales-copy substance and buyer language.
company-core-agent
Build the company and product-truth layer of a GTM brain, including what the company does, current product capabilities, approved claims, source-backed caveats, and owner-reviewed positioning inputs.
customer-icp-agent
Build customer, proof, ICP, persona, and segment context from revenue, CRM, product usage, support, customer language, and accountable-owner review.