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 Frontal-so/outbound-skills --skill email-infragit clone --depth 1 https://github.com/Frontal-so/outbound-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/frontal-so/outbound-skills/email-infra)<a href="https://agentmods.dev/skills/frontal-so/outbound-skills/email-infra"><img src="https://agentmods.dev/badge/skills/frontal-so/outbound-skills/email-infra/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/frontal-so/outbound-skills/email-infra"><img src="https://agentmods.dev/badge/skills/frontal-so/outbound-skills/email-infra.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.00215 | $0.00940 |
| Opus 5 | $0.00108 | $0.00470 |
| Sonnet 5 | $0.00043 | $0.00188 |
| Haiku 4.5 | $0.00021 | $0.00094 |
Grade A, and why
email-infra 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Infrastructure
You help users set up, configure, and troubleshoot cold email infrastructure from zero to live campaigns.
Reference
Read these resources based on the user's question:
- Complete setup guide: domains, DNS, warmup, monitoring → Read
{SKILL_BASE}/resources/frameworks/email-infra/email-infra-guide.md - Step-by-step walkthroughs with video tutorials → Read
{SKILL_BASE}/resources/frameworks/email-infra/email-infra-step-by-step.md - Diagnosis and recovery for DNS, connection, warmup, deliverability issues → Read
{SKILL_BASE}/resources/frameworks/email-infra/email-infra-troubleshooting.md
Critical Rules (Never Break)
- Never use primary domain for cold outreach
- Max 2 mailboxes per domain
- One domain = one workspace (never mix)
- Use multiple registrars (no single point of failure)
- Warm up 2-3 weeks minimum before sending
- Never disable warm-up once campaigns running
- Start conservative, scale gradually
Infrastructure Sizing Formula
- Monthly goal / 20 working days = daily volume
- Daily volume / 20-25 per mailbox = mailboxes needed
- Mailboxes x 1.5 (buffer) / 2 = domains needed
- Provider split: 60% Google Workspace, 40% Microsoft 365
DNS (All 4 Records Required)
| Record | Purpose |
|---|---|
| MX | Routes incoming email |
| SPF | Declares sending servers |
| DKIM | Digital signature authentication |
| DMARC | Policy for SPF/DKIM failures |
Warmup Timeline
- Week 1: Foundation (no campaigns)
- Week 2: Building (no campaigns)
- Week 3: Ready (health scores 70%+, ideally 90%+)
Going Live Ramp Schedule
| Week | Microsoft | |
|---|---|---|
| 1 | 10-15/day | 5-10/day |
| 2-3 | 15-20/day | 10-12/day |
| 4+ | 20-25/day | 12-15/day |
Healthy Metrics
- Open rate: 50%+
- Reply rate: 2%+
- Bounce rate: <3% (target <2%)
- Spam rate: <0.1%
- Deliverability score: >95%
Examples
Example 1: "I want to send 3,000 emails per month, how many domains do I need?" → Read email-infra-guide.md. Calculate: 150/day → 10-12 mailboxes → 5-6 domains. Split 60/40 Google/Microsoft.
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 · 81 lines · 215 tokens per session scan A 46087535b3b5
email-infra is a skill published in the GitHub repository Frontal-so/outbound-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 215 tokens to every session and 940 once invoked, about $0.0011 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
audience-icp-filter
Filter an existing audience or lead list against your ICP and split it into ready-to-sequence segments. Use when someone already has a list of people — an audience in their sales tool, a CSV or CRM export, event or webinar attendees, registrants, a Sales Navigator import, a newsletter or community export — and wants…
team-performance-dashboard
Generate your Team Performance Dashboard from your La Growth Machine data: a head-of-sales cockpit that ranks each sender (rep) on reply rate, your success event (signups/meetings/deals) and conversion, surfaces hot leads going cold, and turns your best reps' campaigns into a coaching playbook for the rest. Pulls only…
weekly-performance-advisor
Generate your Weekly Performance Advisor dashboard from your La Growth Machine data: a two-tab cockpit (To do + Weekly performance) that flags campaigns to fix, sorts replies by urgency, and tracks reply volume week over week. It pulls only YOUR live LGM data, scores each running campaign against baked 3-zone…
objection-analyzer
Find out which objections your outbound gets, how well your team handled them, and what to say next time. Use whenever the user wants to analyze the objections in their replies, rank the most frequent ones, know how to handle a specific objection, coach reps on their objection answers, build an objection playbook or…
sales-nav-search-builder
Generate a precise LinkedIn Sales Navigator search URL from a natural-language ICP description — for sales prospecting, outbound outreach, lead generation, and B2B targeting. Use whenever the user asks for a Sales Nav URL, a LinkedIn search URL, an outbound prospecting query, a search for a persona or role, wants to…
reply-draft-assistant
Handle replies to your cold outreach end to end — classify each response, draft the right answer from the full conversation, and send it through La Growth Machine after you approve. Use any time the user has replies to handle: their LGM inbox ("who do I need to reply to?"), a campaign's replies, or a pasted thread.…