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 domain-infrastructuregit 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/domain-infrastructure)<a href="https://agentmods.dev/skills/leadmagic/gtm-skills/domain-infrastructure"><img src="https://agentmods.dev/badge/skills/leadmagic/gtm-skills/domain-infrastructure/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/domain-infrastructure"><img src="https://agentmods.dev/badge/skills/leadmagic/gtm-skills/domain-infrastructure.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.00108 | $0.05065 |
| Opus 5.5 | $0.00043 | $0.02026 |
| Sonnet 5.5 | $0.00022 | $0.01013 |
| Haiku 4.5 | $0.00011 | $0.00507 |
Grade A, and why
domain-infrastructure 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 15d 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 — 496 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Infrastructure
Overview
Cold email deliverability depends entirely on infrastructure decisions made before the first email is sent. The domain names, mailbox providers, DNS configuration, and rotation strategy form the foundation on which all outbound rests. A poor infrastructure setup will produce poor deliverability regardless of copy quality or targeting precision.
This skill produces a complete domain infrastructure plan: which secondary domains to register, how to provision mailboxes across providers (Google Workspace, Microsoft 365, Zoho), DNS authentication configuration for each domain, inbox rotation schedules, and a monitoring framework to detect degradation before it impacts campaigns.
The non-obvious rule: never send cold email from your primary business domain. Your primary domain carries your transactional email (password resets, invoices, customer notifications, support tickets) and your corporate email (sales, support, executives). A reputation hit on the primary domain from cold email complaints or bounces takes down ALL of those functions simultaneously. Cold email must operate on entirely separate, isolated infrastructure.
When to Use
- User says "set up domains for cold email" or "buy sending domains" → activate this skill
- User asks "how many domains do I need" or "how many mailboxes per domain" → activate this skill
- User wants to "provision mailboxes for outreach" or "set up Google Workspace for outbound" → activate this skill
- User mentions "DNS configuration for email," "inbox rotation," or "primary domain isolation" → activate this skill
- User asks "should I use Google or Microsoft for cold email" or "Zoho vs Gmail for outreach" → activate this skill
- User wants to "scale sending capacity" or "add more mailboxes" → activate this skill
Do NOT use for:
- Configuring SPF/DKIM/DMARC records → use
email-deliverability(domain-infrastructure tells you WHICH domains and mailboxes; email-deliverability configures authentication ON them) - Selecting a sending platform → use
sending-platforms - Designing email sequences → use
cold-email-strategy
What ships with it
7 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.
- 15d ago Changed b9a6ced6ea90
- 1mo ago First seen · 496 lines · 108 tokens per session scan A f24f37f64ac0
domain-infrastructure is a skill published in the GitHub repository LeadMagic/gtm-skills (64 stars, last pushed 2d ago), licensed MIT. It adds 108 tokens to every session and 5,065 once invoked, about $0.0004 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…
startup-launch-playbook
A step-by-step playbook for early-stage startups going from pre-seed to their first 1000 users. Covers MVP validation, initial traction channels, and founder-led growth tactics. By @WeiYipei — follow on X for more startup growth insights.
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…