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 multi-sender-rotationgit 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/multi-sender-rotation)<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/multi-sender-rotation"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/multi-sender-rotation/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/multi-sender-rotation"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/multi-sender-rotation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00075 | $0.00658 |
| Opus 5 | $0.00037 | $0.00329 |
| Sonnet 5 | $0.00015 | $0.00132 |
| Haiku 4.5 | $0.00007 | $0.00066 |
Grade A, and why
multi-sender-rotation 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 9d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run this when campaign volume exceeds what one account can safely send. It produces a sender-pool plan: how many accounts, how leads are split, per-account caps, and what happens when an account degrades.
The play
- Size the pool from the target, not the other way around: divide required daily connection requests by 20, the safe steady-state ceiling per warmed account. A 100-invite-per-day campaign is a 5-account pool.
- Only rotate warmed accounts. A new profile joins the pool after a full warm-up ramp, never on day one. Keep one warmed spare per five active senders: the bench rule. When an account degrades, the bench replaces it the same day.
- Split the lead list by account, never round-robin per message. Each prospect belongs to exactly one sender for the entire relationship: the one-voice rule. Dedupe by person and by company before launch so two senders never hit the same account.
- Stagger sending windows so the pool does not fire in one burst: each account keeps its own working hours, matched to its own timezone and history.
- Keep per-account caps individual. An account fresh off warm-up sends less than a veteran; never apply the pool average to every profile.
- On any warning: pull that account from rotation immediately, pause it 48-72 hours, and let the bench absorb its remaining volume. Never redistribute a paused account's leads mid-conversation; conversations wait for their owner.
- Review the pool weekly: acceptance rate and reply rate per account. One account trending down while others hold is an account problem; all accounts trending down together is a targeting or copy problem.
What good looks like
- Experienced operators read per-account acceptance rates as an early-warning system; the mediocre version only watches campaign totals and misses the one account quietly dying inside a healthy average.
- The common mistake is treating the pool as one big account: shared caps, shared list, leads bouncing between senders. Prospects notice a second stranger continuing a first stranger's conversation, and so does the platform.
- Done well, losing any single account costs at most one-fifth of daily volume for two days, no prospect ever hears from two different senders, and the campaign total stays flat while individual accounts rest and rotate.
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.
- 9d ago First seen · 39 lines · 75 tokens per session scan A 19571374ffcd
multi-sender-rotation is a skill published in the GitHub repository swan-gtm/gtm-skills (153 stars, last pushed 2d ago), licensed MIT. It adds 75 tokens to every session and 658 once invoked, about $0.0004 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-03.
Other skills, from other repositories
afrexai-lead-hunter
Enterprise-grade B2B lead generation, enrichment, scoring, and outreach sequencing for AI agents. Find ideal prospects, enrich with verified data, score against your ICP, and generate personalized outreach — all autonomously.
cold-outreach
Use when writing a cold email or LinkedIn DM to a stranger and its cadence: first-touch copy under a word ceiling, 4-7 step bump sequences, per-inbox volume and warm-up limits, the compliant opt-out footer. NOT SPF/DKIM/DMARC setup (that is email-deliverability), NOT sourcing the list (that is lead-gen), NOT life…
distributor-outreach-email
Writes a sales outreach email to a film or content distributor introducing a completed project for acquisition consideration, including key commercial information an acquisitions team needs to evaluate the opportunity.
ai-cold-email
Generate personalized cold outreach emails using AI.
cold-email-personalizer
A tool that writes personalised cold emails, which are unsolicited messages sent to potential customers or partners, using information about each person.
outreach-strategist
Reviews and coaches your outreach with specific scoring, feedback, and rewrites.