agentmods.dev

setting-up-sending-domain

setting-up-sending-domain is a skill for Claude Code, Codex from mailtrap/mailtrap-skills. It costs 44 tokens per session (1,146 once invoked), scanned A, original, MIT.

A guide for adding and verifying a sending domain, the domain used in the From address of live email.

In plain words
What is it for?
Use it to set up or troubleshoot domain verification with DNS providers, handle DNS propagation, complete compliance steps, and configure click tracking.
Why use it?
It explains the DNS and compliance steps needed before an email service can send messages from a domain you control.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 10repo 1mo ago A scan 44 tokens original MIT

Good fit Use it to set up or troubleshoot domain verification with DNS providers, handle DNS propagation, complete compliance steps, and configure click tracking.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mailtrap/mailtrap-skills/setting-up-sending-domain
View source ↗ mailtrap/mailtrap-skills mailtrap.io
Install

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.

Any agent
npx skills add mailtrap/mailtrap-skills --skill setting-up-sending-domain
Clone the repo
git clone --depth 1 https://github.com/mailtrap/mailtrap-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for setting-up-sending-domain

README.md
[![agentmods](https://agentmods.dev/badge/skills/mailtrap/mailtrap-skills/setting-up-sending-domain/github.svg)](https://agentmods.dev/skills/mailtrap/mailtrap-skills/setting-up-sending-domain)
Your own site
<a href="https://agentmods.dev/skills/mailtrap/mailtrap-skills/setting-up-sending-domain"><img src="https://agentmods.dev/badge/skills/mailtrap/mailtrap-skills/setting-up-sending-domain/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.

agentmods 80×15 button for setting-up-sending-domain

Your own site · 80×15
<a href="https://agentmods.dev/skills/mailtrap/mailtrap-skills/setting-up-sending-domain"><img src="https://agentmods.dev/badge/skills/mailtrap/mailtrap-skills/setting-up-sending-domain.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,146 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.01146
Opus 5 $0.00022 $0.00573
Sonnet 5 $0.00009 $0.00229
Haiku 4.5 $0.00004 $0.00115

Measured 12d ago against content hash 8fbe6b442e23, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

setting-up-sending-domain 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 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.

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.

skills/setting-up-sending-domain/SKILL.md · 74 lines

How it starts

The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Setting up a Mailtrap sending domain

Overview

You must add and verify a domain you control before live sending. Mailtrap shows every DNS record required for that domain in the UI: add the complete set as given (do not cherry-pick). After DNS verifies, complete the compliance step if requested.

Subdomain vs root: add the exact hostname you will use in the From address. If you send from notifications.mycompany.com, add that subdomain as the sending domain—not only mycompany.com, unless you truly send from the root domain.

For step-by-step clicks at common hosts, open the matching guide on Sending domain setup (Cloudflare, Route 53, etc.) and follow it alongside the live UI values.

Related skills: authorizing-api-requests (tokens, env vars, account_id resolution), sending-emails (after domain is ready).

When to use

  • New Sending Domains setup, stuck verification, or compliance questions
  • DNS at Cloudflare, AWS, Google, Namecheap, GoDaddy, DigitalOcean, etc.

When not to use

  • Sandbox-only testing without a custom domain (see testing-with-sandbox)

Authorization

The Sending Domains API calls below need Authorization: Bearer $MAILTRAP_API_TOKEN and an $MAILTRAP_ACCOUNT_ID in the path. Token scope, storage, and the one-liner that resolves $MAILTRAP_ACCOUNT_ID from GET https://mailtrap.io/api/accounts are covered in skill authorizing-api-requests.

Automating setup (API and DNS providers)

Prefer this path when building scripts or AI-assisted automation:

  1. DNS records and status via API — Use the Sending Domains API:
  • GET https://mailtrap.io/api/accounts/$MAILTRAP_ACCOUNT_ID/sending_domains — lists domains
  • GET https://mailtrap.io/api/accounts/$MAILTRAP_ACCOUNT_ID/sending_domains/{sending_domain_id} — returns dns_records (each with type, name, value, and verification status) and dns_verified. Poll after you publish DNS.
  1. Create domain via API —
  • POST https://mailtrap.io/api/accounts/$MAILTRAP_ACCOUNT_ID/sending_domains with domain_name when your flow provisions domains programmatically.
  1. Publish DNS programmatically —
  • Create the returned records at your DNS host using their API (e.g., Cloudflare API, AWS Route 53, Google Cloud DNS) or IaC. Align record names and values exactly with the API response.

Read the full file on GitHub · 74 lines

Changes

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.

  1. 12d ago First seen · 74 lines · 44 tokens per session scan A 8fbe6b442e23

Subscribe to this mod's changes

setting-up-sending-domain is a skill published in the GitHub repository mailtrap/mailtrap-skills (10 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 1,146 once invoked, about $0.0002 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.

CloudDevOps and cloudMarketing and SEO
Related

Other skills, from other repositories

gke-compute-classes

Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…

google/skills · 83 tokens

gke-reliability

Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).

google/skills · 73 tokens

gke-workload-security

Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…

google/skills · 181 tokens

nemo-automodel-launcher-config

Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.

NVIDIA/skills · 30 tokens

azure-mgmt-botservice-dotnet

Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".

microsoft/skills · 78 tokens

cloud-architect

Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…

Jeffallan/claude-skills · 71 tokens