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 LeadMagic/gtm-skills --skill email-deliverabilitygit clone --depth 1 https://github.com/LeadMagic/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/leadmagic/gtm-skills/email-deliverability)<a href="https://agentmods.dev/skills/leadmagic/gtm-skills/email-deliverability"><img src="https://agentmods.dev/badge/skills/leadmagic/gtm-skills/email-deliverability/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/leadmagic/gtm-skills/email-deliverability"><img src="https://agentmods.dev/badge/skills/leadmagic/gtm-skills/email-deliverability.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.00116 | $0.05235 |
| Opus 5.5 | $0.00046 | $0.02094 |
| Sonnet 5.5 | $0.00023 | $0.01047 |
| Haiku 4.5 | $0.00012 | $0.00524 |
Grade A, and why
email-deliverability 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 26d 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 — 497 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Deliverability
Overview
Deliverability is the foundation on which all outbound email rests. Without it, the best copy, the most sophisticated sequence, and the highest-quality list produce zero pipeline — because the email never reaches the inbox. The inbox placement rate is the single most important metric in cold email, and it is entirely a function of technical configuration plus ongoing reputation management.
This skill produces a deliverability setup and monitoring plan: DNS authentication configuration (SPF, DKIM, DMARC), a 4-week warmup schedule with per-week volume targets, reputation monitoring protocols, bounce and complaint handling procedures, and a deliverability health dashboard definition. It covers the full lifecycle from initial setup through ongoing maintenance.
The non-obvious rule: most deliverability problems are not technical. They are behavioral. Sending too many emails too fast, sending to unverified addresses, sending from a primary domain, or ignoring bounce spikes will defeat even perfect DNS configuration. Deliverability is 30% setup and 70% discipline.
CRITICAL: Never describe validation internals. Email validation is a blackbox subject — this skill covers the strategy of validation (when to validate, how to handle results) but NEVER describes how validation algorithms work.
When to Use
- User says "set up SPF/DKIM/DMARC" or "configure DNS for email" → activate this skill
- User asks "how do I warm up a domain" or "what's the warmup schedule" → activate this skill
- User reports "my emails are going to spam" or "open rates dropped" → activate this skill
- User asks about "bounce rate targets," "complaint handling," or "reputation monitoring" → activate this skill
- User wants to "check domain reputation" or "set up DMARC monitoring" → activate this skill
- User asks "how many emails per day per mailbox" → activate this skill
Do NOT use for:
- Buying and configuring secondary domains and mailboxes →
use
domain-infrastructure - Selecting a sending platform → use
sending-platforms - Designing the email sequence → use
cold-email-strategy - Writing email copy → use
cold-email-copywriting
What ships with it
8 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.
- references/bounce-complaint-procedures.md 1.8 KB
- references/deliverability-primer.md 2.4 KB
- references/eric-nowoslawski-outbound.md 11 KB
- references/framework-notes.md 965 B
- references/output-artifacts.md 1.5 KB
- references/sending-limits-reference.md 851 B
- scripts/check-output.py 863 B runs code
- templates/output-template.md 1.4 KB
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.
- 26d ago Changed d8905d2a8a0e
- 1mo ago First seen · 497 lines · 116 tokens per session scan A 8dd6cd4255fc
email-deliverability is a skill published in the GitHub repository LeadMagic/gtm-skills (69 stars, last pushed 13d ago), licensed MIT. It adds 116 tokens to every session and 5,235 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
ai-gtm-transformation-audit
Use this skill when a GTM leader (CRO, CMO, VP Sales, RevOps, CS leader, founder) wants to know where their organization really stands on its AI GTM transformation, what is holding it there, and what to do in the next 30 days to move up. It runs a short structured interview, places the org on one of four levels…
event-lead-ingestion
Use this skill when a teammate pastes a LinkedIn URL or work email for someone they just met at a booth, dinner or conference hallway and wants that lead captured the same way every time. It resolves the person and company, checks relationship history before scoring, writes the CRM record and a structured conversation…
competitor-monitoring
Use this skill when you need to know what rival companies are doing — "what are my competitors doing", "competitor update", "competitor news", "competitive landscape", "market intel", "what's new with [company]", "track [company]", "competitor briefing", "who's making moves", "we keep losing deals to [company]" — or…
event-room-intelligence
Use this skill 1 to 3 days before any face-to-face event where you hold a registration export (a talk, conference, dinner, booth) and the question is 'I have the attendee CSV, who should I talk to?'. It maps every registrant to a company, joins the list against the live CRM, LinkedIn-verifies every person's title and…
multichannel-campaign-builder
Use this skill when someone needs a complete outbound sequence written — every touch across LinkedIn and email, not a single cold email. Produces three distinct angles to choose from, then the full sequence with each message ready to send, calibrated to the campaign type and channel mix and self-checked against a…
event-account-plan
Use this skill in the weeks before a conference, trade show, or field event, when an attendee or registration list exists and the question is which companies to work, who to talk to at each one, and what to say. Trigger on "we have the attendee list for the show", "who should we target at this conference", "build the…