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 swan-gtm/gtm-skills --skill call-followup-sweepgit clone --depth 1 https://github.com/swan-gtm/gtm-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/swan-gtm/gtm-skills/call-followup-sweep)<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/call-followup-sweep"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/call-followup-sweep/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/swan-gtm/gtm-skills/call-followup-sweep"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/call-followup-sweep.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.00150 | $0.01179 |
| Opus 5 | $0.00075 | $0.00589 |
| Sonnet 5 | $0.00030 | $0.00236 |
| Haiku 4.5 | $0.00015 | $0.00118 |
Grade A, and why
call-followup-sweep 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 yesterday.
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.
Applies when a batch of customer calls has happened and the follow-through is owed. Produces a per-account draft for the calls that earn one, a no-email list with reasons for the calls that don't, and an aging report of commitments still open from prior sweeps. Nothing is ever sent.
The sweep
- Ask the window before anything else. Day or week — never guess, and never default to "all recent calls". The window changes the output: a day sweep is mostly fresh drafts while the call is still warm; a week sweep is mostly an aging and pattern report with fewer, denser drafts. If the answer is "week", confirm whether it means the trailing five business days or the calendar week — on a Wednesday those differ by half a book.
- Pull every call in the window from wherever calls are recorded — transcripts, recordings, or the user's own notes. Capture account, attendees, date, and duration for each. A scheduled call with no recording is a finding, not a gap: list it as unverified rather than dropping it silently.
- Extract commitments, not summary. Read
references/commitment-extraction.mdbefore the first call. Four things get pulled from every transcript — what you committed to, what they committed to, the question you didn't answer, and any date that was named out loud. The first category is the one that loses deals and the one reps skip. - Triage which calls earn an email. Read
references/triage-rubric.md. Most calls in a given week do not. The value of a sweep is subtraction — a run that drafts an email for every call has done nothing a calendar couldn't. - Dedupe by account, not by call. Three calls with one account in one week is one email to that account, built from all three. Separate drafts to the same company arriving the same morning read as an unmanaged vendor.
- Draft to the call's shape. Read
references/draft-patterns.md— the email a stalled renewal needs is not the email a first discovery needs. Cap every draft at 150 words and three visible action items; overflow goes to a named next call, not a longer email. - Report the sweep, don't just dump drafts. Lead with commitments aged past three business days, then the drafts, then the no-email list with a one-line reason each, then any pattern that showed up across calls — the same objection landing three times in a week is worth more than any single draft.
What ships with it
3 files 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.
- yesterday First seen · 87 lines · 150 tokens per session scan A 2b8ed05e2f75
call-followup-sweep is a skill published in the GitHub repository swan-gtm/gtm-skills (150 stars, last pushed 2d ago), licensed MIT. It adds 150 tokens to every session and 1,179 once invoked, about $0.0007 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-09-11.
Other skills, from other repositories
revenue-team-onboarding
Revenue team onboarding — security access provisioning, ramp schedules, 30-60-90 plans, Slack engagement, shadowing, certification, and time-to-first-meeting reduction. Use when onboarding SDRs, AEs, managers, or RevOps hires. Triggers on: "sales onboarding", "SDR ramp", "30-60-90 sales", "reduce ramp time", "Slack…
team-management
Team management for startup leaders — 1:1s, performance reviews, goal setting (OKRs), delegation, feedback culture, remote team management, team rituals, and scaling from IC to manager. Use when building team processes, managing first direct reports, or scaling management as the company grows. Triggers on: "team…
brief-me-for-today
Wake up with a one-screen brief: today's meetings, drafts waiting on your sign-off, the top three moves I'd make today, and your watch list of stalled deals or red customers. Calendar is the anchor; I never invent meetings.
Pipedrive Automation
Automate Pipedrive CRM workflows including deal management, pipeline tracking, and sales reporting.
business-growth-skills
Router/index for the 4 business & growth skills bundled in this plugin: customer-success-manager (health scoring, churn risk, expansion), sales-engineer (RFP analysis, competitive matrices, PoC planning), revenue-operations (pipeline, forecast accuracy, GTM efficiency), and contract-and-proposal-writer. Use when a…
prospecting-time-block-planner
Build a protected weekly prospecting calendar that separates Golden Hours (when buyers are buying) from Platinum Hours (before/after business hours for research and admin), calculates what each Golden Hour is worth in dollars, and installs a Power Hour protocol that eliminates distractions during focused dial blocks.…