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 AlexisMarasigan/coldoutboundskills --skill zapmail-domain-setup-publicgit clone --depth 1 https://github.com/AlexisMarasigan/coldoutboundskillsWrote 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/alexismarasigan/coldoutboundskills/zapmail-domain-setup-public)<a href="https://agentmods.dev/skills/alexismarasigan/coldoutboundskills/zapmail-domain-setup-public"><img src="https://agentmods.dev/badge/skills/alexismarasigan/coldoutboundskills/zapmail-domain-setup-public/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/alexismarasigan/coldoutboundskills/zapmail-domain-setup-public"><img src="https://agentmods.dev/badge/skills/alexismarasigan/coldoutboundskills/zapmail-domain-setup-public.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.00065 | $0.04366 |
| Opus 5 | $0.00032 | $0.02183 |
| Sonnet 5 | $0.00013 | $0.00873 |
| Haiku 4.5 | $0.00006 | $0.00437 |
Grade A, and why
zapmail-domain-setup-public scanned grade A with 1 finding 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 12d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**CRITICAL: Comma encoding bug.** When building the URL in Python, default `urllib.parse.urlencode()` encodes commas as `%2C`, which breaks the batch request. Fix: This is a copy
100% identical to zapmail-domain-setup-public — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 461 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cold Email Domain Setup: Dynadot + Zapmail (Public Edition)
Complete workflow to generate short domain names, purchase them on Dynadot, and set them up on Zapmail with inboxes ready for cold email sending.
First-Time Setup (Onboarding)
Before running anything, you need two API keys stored as environment variables.
1. Get Your Dynadot API Key
- Log into dynadot.com
- Go to Tools > API in the left sidebar
- Enable API access and copy your API key
- Whitelist your IP address (required by Dynadot)
2. Get Your Zapmail API Key
- Log into zapmail.ai
- Go to Settings > API
- Copy your API key
3. Store Your Keys
Add these to a .env file in your project root (or export them in your shell):
# .env — NEVER commit this file
DYNADOT_API_KEY=your_dynadot_key_here
ZAPMAIL_API_KEY=your_zapmail_key_here
Load them in your script:
import os
from dotenv import load_dotenv
load_dotenv()
DYNADOT_API_KEY = os.environ["DYNADOT_API_KEY"]
ZAPMAIL_API_KEY = os.environ["ZAPMAIL_API_KEY"]
4. Verify Access
Test both APIs before doing anything:
Dynadot — check wallet balance:
GET https://api.dynadot.com/api3.json?key=<YOUR_KEY>&command=account_info
Response includes AccountBalance (e.g., "$106.20").
Zapmail — list domains:
GET https://api.zapmail.ai/api/v2/domains/assignable?limit=10&page=1
Header: x-auth-zapmail: <YOUR_KEY>
If both return 200, you're ready.
Full Workflow Overview
Step 1: Generate domain name candidates ~instant
Step 2: Check availability on Dynadot ~1 min per 500 domains
Step 3: Purchase available domains ~1 min per 100 domains
| (domains now registered on Dynadot)
Step 4: Switch nameservers to Zapmail ~1 min per 500 domains
| WAIT 15-20 minutes for DNS propagation
Step 5: Connect domains on Zapmail ~2 min per 500 domains
| WAIT 10-30 minutes for domains to become assignable
Step 6: Create inboxes on Zapmail ~3 min per 500 domains
| WAIT 4-6 HOURS for inbox provisioning
Step 7: Export to your email sending platform ~instant
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.
- 12d ago First seen · 461 lines · 65 tokens per session scan A 98f5944f9d13
zapmail-domain-setup-public is a skill published in the GitHub repository AlexisMarasigan/coldoutboundskills (4 stars, last pushed 4mo ago), licensed MIT. It adds 65 tokens to every session and 4,366 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to zapmail-domain-setup-public, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…