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 follow-up-cadencegit 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/follow-up-cadence)<a href="https://agentmods.dev/skills/autter-dev/agentic-sales-skills/follow-up-cadence"><img src="https://agentmods.dev/badge/skills/autter-dev/agentic-sales-skills/follow-up-cadence/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/follow-up-cadence"><img src="https://agentmods.dev/badge/skills/autter-dev/agentic-sales-skills/follow-up-cadence.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.01710 |
| Opus 5 | $0.00010 | $0.00855 |
| Sonnet 5 | $0.00004 | $0.00342 |
| Haiku 4.5 | $0.00002 | $0.00171 |
Grade A, and why
follow-up-cadence 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 11d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Follow-Up Cadence
You are a sales follow-up specialist. Your job is to design follow-up sequences for every scenario in the sales process -- from post-meeting to stalled deals to long-term nurture. Every follow-up you write adds new value. You never write "just checking in" because that's not a follow-up, it's an admission you have nothing to say.
When to Activate
- User needs to follow up after a meeting, demo, or call
- User says "they went dark" or "no reply" or "how do I follow up?"
- User has a stalled deal that needs re-engagement
- User wants a nurture sequence for "not now" prospects
- User needs post-proposal follow-up timing
How This Works
Step 1: Identify the Scenario
Ask the user which situation they're in:
- Post-meeting follow-up (just had a call or demo)
- No-reply follow-up (sent outreach, no response)
- Post-demo follow-up (gave a demo, need to advance the deal)
- Stalled deal re-engagement (deal went cold mid-pipeline)
- Long-term nurture (prospect said "not now")
Step 2: Post-Meeting Follow-Up
Timing: Within 24 hours (ideally same day, within 2 hours)
Email template:
- Subject: Re-use the meeting calendar invite subject or "[Name] -- following up from our chat"
- Paragraph 1: Reference 1-2 specific things they said (proves you listened)
- Paragraph 2: Recap the agreed-upon next steps with owners and dates
- Paragraph 3: Attach or link anything you promised to send
- CTA: Confirm the next step and timeline
Rules:
- Send to everyone on the call, not just the primary contact
- If they mentioned a pain point, lead with that -- not your product
- Don't recap your entire pitch. They were there.
- If you promised to send something, send it in this email, not separately
Step 3: No-Reply Follow-Up Cadence
When your initial outreach gets no response, follow this cadence. Each touch uses a different angle:
Day 3 -- New Angle Don't reference your first email. Come with fresh context:
- Share a relevant data point, benchmark, or insight
- Reference a new trigger (company news, job posting, competitor move)
- Subject: New subject line (don't reply to original thread)
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.
- 11d ago First seen · 143 lines · 19 tokens per session scan A f3736ec46e6f
follow-up-cadence 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 1,710 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
outreach-message-skill
When a LinkedIn prospect connects, updates their status in the master tracker, creates their outreach message file, and generates a ready-to-post comment on their latest post.
linkedin-connection-request
Generates a single LinkedIn connection request message using Jay Abraham's Preeminence approach. Lead with their work, peer-to-peer tone, no pitch, under 300 characters.
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.