deliverability-monitoring

deliverability-monitoring is a skill for Claude Code from LeadMagic/gtm-skills. It costs 67 tokens per session (5,686 once invoked), scanned A, original, MIT.

A guide for watching the health of outbound email infrastructure, including sending domains, inboxes, bounces, spam placement, replies, and reputation signals. Email deliverability means whether messages reach the inbox instead of spam or being blocked.

In plain words
What is it for?
Use it to define email-health alerts, review bounce and spam placement data, check SPF, DKIM, and DMARC authentication, monitor blacklists, and plan recovery steps.
Why use it?
It helps detect delivery and reputation problems before they appear as a large drop in pipeline. It also distinguishes a message reaching a mailbox from a message actually reaching the inbox.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code; mentions Codex; mentions Gemini CLI.

Part of the gtm-skills plugin — 196 skills shipped together

Good fit Use it to define email-health alerts, review bounce and spam placement data, check SPF, DKIM, and DMARC authentication, monitor blacklists, and plan recovery steps.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/leadmagic/gtm-skills/deliverability-monitoring
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 LeadMagic/gtm-skills --skill deliverability-monitoring
Clone the repo
git clone --depth 1 https://github.com/LeadMagic/gtm-skills

Made for: Claude Code.

Or install gtm-skills, the plugin that ships this one along with the rest of its 196 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 deliverability-monitoring

README.md
[![agentmods](https://agentmods.dev/badge/skills/leadmagic/gtm-skills/deliverability-monitoring/github.svg)](https://agentmods.dev/skills/leadmagic/gtm-skills/deliverability-monitoring)
Your own site
<a href="https://agentmods.dev/skills/leadmagic/gtm-skills/deliverability-monitoring"><img src="https://agentmods.dev/badge/skills/leadmagic/gtm-skills/deliverability-monitoring/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 deliverability-monitoring

Your own site · 80×15
<a href="https://agentmods.dev/skills/leadmagic/gtm-skills/deliverability-monitoring"><img src="https://agentmods.dev/badge/skills/leadmagic/gtm-skills/deliverability-monitoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,686 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00067 $0.05686
Opus 5 $0.00034 $0.02843
Sonnet 5 $0.00013 $0.01137
Haiku 4.5 $0.00007 $0.00569

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

Security

Grade A, and why

deliverability-monitoring 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 4d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/check-output.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/analytics/deliverability-monitoring/SKILL.md · 391 lines

How it starts

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

Deliverability Monitoring

Overview

Deliverability Monitoring provides continuous surveillance of email infrastructure health — the foundation on which all outbound GTM rests. The core principle is that deliverability problems compound silently: by the time you notice lower reply rates, reputation damage may already be weeks deep and require months to repair. This skill prevents the catastrophic mistake of discovering deliverability issues through pipeline decline rather than proactive monitoring.

The non-obvious rule: deliverability is not binary (delivered vs bounced). It exists on a spectrum — inbox vs spam folder vs promotions tab vs graymail vs blocked. A "delivered" email that lands in the spam folder is effectively undelivered. This skill measures inbox placement, not just delivery status.

This skill produces a Domain Health Dashboard with: real-time bounce tracking across all sending domains, spam placement rates by mailbox provider, blacklist status across 50+ blacklists, DMARC aggregate report analysis with forwarding source identification, authentication health scores (SPF/DKIM/DMARC), and predictive reputation trend alerts.

When to Use

  • User says "check my deliverability" or "domain health check" → activate this skill
  • User mentions "bounce rate is high" or "emails going to spam" → use this skill for diagnosis
  • User asks "is my domain blacklisted" or "blacklist check" → activate monitoring module
  • User says "DMARC reports" or "who is sending as my domain" → run DMARC analysis
  • User mentions "spam placement" or "inbox rate" → track placement by provider
  • User asks "domain reputation" or "sender score" → check reputation scores
  • Trigger phrases: email deliverability, bounce tracking, spam folder, sender reputation, email authentication, DKIM SPF, domain warming, inbox placement test

Do NOT use for:

  • Setting up DNS authentication initially → use domain-infrastructure
  • Writing relevant, permission-aware email content → use cold-email-copywriting
  • Campaign performance analysis (opens, replies, meetings) → use campaign-analytics
  • Choosing or configuring sending platforms → use sending-platforms
  • Sequence design or cadence → use cold-email-strategy

Read the full file on GitHub · 391 lines

Files

What ships with it

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

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. 4d ago Changed 320d046dab79
  2. 8d ago Changed ee2abfa2e769
  3. 12d ago First seen · 391 lines · 67 tokens per session scan A 509ef58787d6

Subscribe to this mod's changes

deliverability-monitoring is a skill published in the GitHub repository LeadMagic/gtm-skills (50 stars, last pushed 5d ago), licensed MIT. It adds 67 tokens to every session and 5,686 once invoked, about $0.0003 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-30.

Related

Other skills, from other repositories

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…

swan-gtm/gtm-skills · 167 tokens

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…

swan-gtm/gtm-skills · 157 tokens

cialdini-influence

Applies Cialdini's seven principles of ethical persuasion -- Reciprocity, Commitment and Consistency, Social Proof, Authority, Liking, Scarcity, and Unity -- to business contexts including sales, marketing, fundraising, and negotiation. Use when designing conversion funnels, optimizing sales processes, preparing…

fatihguner/foreman · 88 tokens

inbox-digest

Scan the last 48 hours of unread newsletters, news emails, and blog digests. Summarize what's relevant to your work. Trigger when the user asks "what did I miss", "any interesting newsletters", or as part of the morning briefing ritual.

etrebels/claude-code-growth-os · 57 tokens

meeting-prep

Build a pre-meeting briefing — who's in the room, what they care about, your goal, and the questions to ask. Trigger when the user asks to prep for a meeting or call, "what should I know before", or names an upcoming meeting.

etrebels/claude-code-growth-os · 56 tokens

retention-feedback

Turn what customer success hears after the sale into product and retention actions. Trigger when an onboarding note, QBR, support thread, or usage review surfaces adoption friction, a churn-risk signal, a feature request that blocks expansion, or a customer who's ready to grow — or when the user says "log this for…

etrebels/claude-code-growth-os · 86 tokens