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 email-1-variations-7git 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/email-1-variations-7)<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/email-1-variations-7"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/email-1-variations-7/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/email-1-variations-7"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/email-1-variations-7.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.00077 | $0.00733 |
| Opus 5.5 | $0.00031 | $0.00293 |
| Sonnet 5.5 | $0.00015 | $0.00147 |
| Haiku 4.5 | $0.00008 | $0.00073 |
Grade A, and why
email-1-variations-7 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 1mo 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
7 Email 1 Variations (Frontal Core Framework)
Variation 1: Observation → Solution → Proof → CTA
[Observation question about their situation?]
[Solution statement.] [Social proof with specific number.]
[Soft CTA question?]
Variation 2: Question → Problem → Solution + Proof → CTA + PS
[Observation question?]
[Problem statement they likely face.]
[Solution + social proof combined.]
[CTA]
PS - [Additional social proof]
Variation 3: First Line → Poke Bear → Value Prop → CTA
[Relevant personalized first line]
[Poke the bear question about their pain?]
We help companies like {{similar_company}} achieve {{result}} without {{obstacle}}.
[CTA]
Variation 4: Trigger → Problem → Solution → Calculation → CTA
[Personalized trigger reference]
[Problem statement]
[Solution]
[Specific calculation showing impact]
[CTA]
Variation 5: Stat → Question → Value CTA
[Industry statistic]
[Question linking stat to their specific problem?]
[Value-based CTA offering resource/insight]
Variation 6: Trigger → Achievement → CTA
[Relevant trigger observation]
[Social proof achievement we delivered for similar company]
[Direct CTA]
Variation 7: Role Pain → Solution → Answer Objection → Soft CTA
What {{title}}s hate about their job: [common pain]
[How we solve it]
[Pre-answer their likely question]
[Very soft CTA]
Email 2 Template (Send 3 Days Later)
Subject: RE: (same thread)
[Lead magnet offer]
[Social proof]
[Value prop restated differently]
[CTA]
Email 3 Template (Send 14 Days Later - New Subject)
Subject: [New subject line]
[New Email 1 variation - different angle]
[Very soft CTA asking for right person]
"If this isn't you, who should I be talking to about {{topic}}?"
Combines with
| Skill | Why |
|---|---|
cold-email-4-sequence |
Slot variations into Email 1 position |
email-writing-frameworks |
Each variation uses different framework |
personalization-hooks |
Add hooks to first line of each variation |
atl-btl-messaging |
Adjust variation for seniority |
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.
- 1mo ago First seen · 166 lines · 77 tokens per session scan A 6181763a4850
email-1-variations-7 is a skill published in the GitHub repository swan-gtm/gtm-skills (220 stars, last pushed 7d ago), licensed MIT. It adds 77 tokens to every session and 733 once invoked, about $0.0003 per session on Opus 5.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
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…
linkedin-outreach
Use when running LinkedIn social selling as a repeatable motion — Sales Navigator saved searches and trigger alerts, weekly request budgets, fixing a low acceptance rate, turning profile views and post engagers into warm threads, logging every touch. NOT the note or DM copy (that is cold-outreach), NOT the deal after…
Cold Email Writer
Write personalized cold outreach emails to hiring managers and founders - specific, human, not a pitch deck.
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.
agent-browser
Drive a real headless Chromium on the workspace host to read pages, fill forms, click buttons, run JS, and take screenshots. Use this whenever you need more than a plain HTTP fetch — pages that require JS to render, pages with an interactive element you have to click through, or when you want an accessibility-tree…
find-leads
Find qualified B2B leads with OpenOutreach — run openoutreach find N [emails], read the CSV it prints on stdout, and hand the rows to whatever sends. Use when the user wants leads, prospects, an ICP-matched contact list, or asks what a campaign already has. Also covers first-run setup (openoutreach init), openoutreach…