verify-email

verify-email is a skill for Claude Code from press-pass/journalism-skills. It costs 27 tokens per session (2,303 once invoked), scanned A, original, MIT.

An email-address checker that tests format, mail-server records, temporary-mail domains, and whether a mailbox appears to exist without sending a message.

In plain words
What is it for?
Use it to check one or more addresses and receive a summary showing which validation steps each address passed or failed.
Why use it?
It helps identify mistyped, undeliverable, or disposable addresses before you use them. This can reduce failed email deliveries without contacting the recipient.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the journalism-skills plugin — 12 skills shipped together

Good fit Use it to check one or more addresses and receive a summary showing which validation steps each address passed or failed.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/press-pass/journalism-skills/verify-email
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 press-pass/journalism-skills --skill verify-email
Clone the repo
git clone --depth 1 https://github.com/press-pass/journalism-skills

Made for: Claude Code.

Or install journalism-skills, the plugin that ships this one along with the rest of its 12 skills.

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 verify-email

README.md
[![agentmods](https://agentmods.dev/badge/skills/press-pass/journalism-skills/verify-email/github.svg)](https://agentmods.dev/skills/press-pass/journalism-skills/verify-email)
Your own site
<a href="https://agentmods.dev/skills/press-pass/journalism-skills/verify-email"><img src="https://agentmods.dev/badge/skills/press-pass/journalism-skills/verify-email/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 verify-email

Your own site · 80×15
<a href="https://agentmods.dev/skills/press-pass/journalism-skills/verify-email"><img src="https://agentmods.dev/badge/skills/press-pass/journalism-skills/verify-email.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,303 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00027 $0.02303
Opus 5 $0.00014 $0.01151
Sonnet 5 $0.00005 $0.00461
Haiku 4.5 $0.00003 $0.00230

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

Security

Grade A, and why

verify-email 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 10d 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.

curl -s -X POST 'https://login.microsoftonline.com/common/GetCredentialType' \
skills/verify-email/SKILL.md · 182 lines

How it starts

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

You will be given one or more email addresses (comma-separated). For each email address, run the verification pipeline below. Report results in a summary table at the end.

Step 1: Syntax check

Verify the email matches a valid format: one @, valid local part (no leading/trailing dots, no consecutive dots), and a valid domain (valid hostname characters, at least one dot).

If the syntax is invalid, mark the email as Invalid (bad syntax) and skip remaining steps.

Step 2: DNS/MX record check

Run dig +short <domain> MX via Bash. Inspect the results:

  • If no MX records are returned, try dig +short <domain> A as a fallback (some domains accept mail on their A record).
  • If neither returns results, mark as Invalid (no mail server) and skip remaining steps.
  • If MX records exist, note the lowest-preference (primary) MX server for Step 4.

Step 3: Disposable email check

Check whether the domain is a known disposable/temporary email provider. Search the web for "is a disposable email" or check against well-known disposable domains (mailinator.com, guerrillamail.com, tempmail.com, throwaway.email, yopmail.com, sharklasers.com, 10minutemail.com, trashmail.com, etc.).

If disposable, flag it as Warning: disposable email provider but continue to Step 4.

Step 4: SMTP RCPT TO verification

This step connects to the mail server and asks if the mailbox exists without sending an email.

Run this Bash script, substituting the email and MX server:

{
  exec 3<>/dev/tcp/<mx_server>/25
  timeout=5

  # Read greeting
  read -t $timeout -u 3 greeting
  echo "GREETING: $greeting"

  # HELO
  echo -e "HELO verify.local\r" >&3
  read -t $timeout -u 3 helo_resp
  echo "HELO: $helo_resp"

  # MAIL FROM
  echo -e "MAIL FROM:<[email protected]>\r" >&3
  read -t $timeout -u 3 mail_resp
  echo "MAIL FROM: $mail_resp"

  # RCPT TO - the actual verification
  echo -e "RCPT TO:<EMAIL_ADDRESS>\r" >&3
  read -t $timeout -u 3 rcpt_resp
  echo "RCPT TO: $rcpt_resp"

  # QUIT
  echo -e "QUIT\r" >&3

  exec 3<&-
  exec 3>&-
} 2>&1

Read the full file on GitHub · 182 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. 10d ago First seen · 182 lines · 27 tokens per session scan A 1ef9625cbce0

Subscribe to this mod's changes

verify-email is a skill published in the GitHub repository press-pass/journalism-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 2,303 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens