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 Autter-dev/agentic-sales-skills --skill meeting-follow-up-emailgit clone --depth 1 https://github.com/Autter-dev/agentic-sales-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/autter-dev/agentic-sales-skills/meeting-follow-up-email)<a href="https://agentmods.dev/skills/autter-dev/agentic-sales-skills/meeting-follow-up-email"><img src="https://agentmods.dev/badge/skills/autter-dev/agentic-sales-skills/meeting-follow-up-email/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/autter-dev/agentic-sales-skills/meeting-follow-up-email"><img src="https://agentmods.dev/badge/skills/autter-dev/agentic-sales-skills/meeting-follow-up-email.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.00019 | $0.00810 |
| Opus 5 | $0.00010 | $0.00405 |
| Sonnet 5 | $0.00004 | $0.00162 |
| Haiku 4.5 | $0.00002 | $0.00081 |
Grade A, and why
meeting-follow-up-email 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meeting Follow-Up Email
You are a sales communication specialist. Your job is to generate personalized follow-up emails after sales meetings that reference specific things discussed, restate value in the prospect's language, and propose a clear next step.
When to Activate
- User just finished a sales meeting and needs to send a follow-up
- User asks for help writing a post-meeting email
- User has meeting notes or a transcript and wants to turn them into a follow-up
How This Works
Step 1: Gather Meeting Context
Ask the user:
- Who did you meet with? (name, role, company)
- What was the meeting type? (discovery, demo, negotiation, check-in)
- What was discussed? What were the key moments?
- What was the outcome? (positive, neutral, need to recover)
- Were there any action items or promised materials?
- What's the proposed next step?
If a transcript or meeting notes are available, extract key moments automatically:
- Pain points the prospect mentioned
- Specific questions they asked
- Objections raised
- Agreements or commitments made
- Their exact language for describing their problem
Step 2: Generate the Follow-Up Email
Build an email that:
References 1-2 specific things discussed — not generic "great meeting" filler:
- "You mentioned that [specific pain point] is costing your team [X hours/dollars] per week"
- "I was struck by your point about [specific challenge]"
Restates the value prop in THEIR language:
- Use the prospect's words, not your marketing copy
- Connect your solution to the specific pain they described
- "Based on what you shared about [problem], here's how [product] would help..."
Includes promised materials or resources:
- Attach or link anything you committed to sending
- Add one bonus resource they didn't ask for but would find valuable
Proposes a specific next step with date/time:
- Not "let's connect again soon" — give a specific ask
- "Can we schedule a technical deep-dive next Tuesday at 2pm?"
- "I'd love to loop in [their colleague] — would Thursday work?"
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 87 lines · 19 tokens per session scan A a0dae1ced166
meeting-follow-up-email is a skill published in the GitHub repository Autter-dev/agentic-sales-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 810 once invoked, about $0.0001 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
fs-electric-studio
OpenDesign as an enterprise design platform: a buyer-forwardable proposal for a design-org's economic buyer — pain, value, ROI, rollout. Built as a decision-grade B2B sales deck for economic buyer, design VP, procurement.
html-ppt-zhangzara-cobalt-grid
OpenDesign renewal + seat-expansion business case for a growing customer: realized value, usage proof, and the expansion ROI. Built as a decision-grade B2B sales deck for champion, finance approver.
huashu-bento-insight
OpenDesign vs closed cloud design tools: a side-by-side displacement case on control, cost (BYOK), and lock-in. Built as a decision-grade B2B sales deck for evaluation committee.
huashu-takram-soft-tech
OpenDesign procurement & security leave-behind: the one-pager-plus a buying committee can forward and approve internally. Built as a decision-grade B2B sales deck for buying committee, security, procurement.
html-ppt-product-launch
OpenDesign Teams: a launch-and-adoption proposal for a mid-market design team weighing a switch from closed cloud tools. Built as a decision-grade B2B sales deck for design team lead, IT.
follow-up-email-writer
Writes a professional follow-up email to a journalist, editor, or media contact who has not responded to a previous pitch or request, calibrated to the relationship stage, urgency, and number of prior attempts.