deliverability-incident-response

deliverability-incident-response is a skill for Claude Code from AlexisMarasigan/coldoutboundskills. It costs 83 tokens per session (2,308 once invoked), scanned A, a copy of deliverability-incident-response, MIT.

A troubleshooting playbook for cold-email delivery problems, such as messages going to spam, high bounce rates, blacklisted domains, blocked warm-up inboxes, or falling replies. It uses a decision tree to connect each symptom with checks and possible fixes.

In plain words
What is it for?
Use it to diagnose spam placement, bounce spikes, blacklisting, warm-up blocks, promotional filtering, and sudden reply-rate drops. It helps decide what to measure first and what corrective action to try.
Why use it?
It gives a clear first response when email performance suddenly changes instead of encouraging random changes. The guidance helps separate list problems, domain reputation issues, infrastructure problems, and message-content issues.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Part of the coldoutboundskills plugin — 28 skills shipped together

Good fit Use it to diagnose spam placement, bounce spikes, blacklisting, warm-up blocks, promotional filtering, and sudden reply-rate drops. It helps decide what to measure first and what corrective action to try.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/alexismarasigan/coldoutboundskills/deliverability-incident-response
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 AlexisMarasigan/coldoutboundskills --skill deliverability-incident-response
Clone the repo
git clone --depth 1 https://github.com/AlexisMarasigan/coldoutboundskills

Made for: Claude Code.

Or install coldoutboundskills, the plugin that ships this one along with the rest of its 28 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-incident-response

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/alexismarasigan/coldoutboundskills/deliverability-incident-response"><img src="https://agentmods.dev/badge/skills/alexismarasigan/coldoutboundskills/deliverability-incident-response.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 83 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,308 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 100% copy Near-identical to another mod 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.00083 $0.02308
Opus 5.5 $0.00033 $0.00923
Sonnet 5.5 $0.00017 $0.00462
Haiku 4.5 $0.00008 $0.00231

Measured 2mo ago against content hash c47d82b98c35, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

deliverability-incident-response 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 2mo 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.

Origin

This is a copy

100% identical to deliverability-incident-response — 92 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.

skills/deliverability-incident-response/SKILL.md · 210 lines

How it starts

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

Deliverability Incident Response

Things break. When they do, you need a playbook — not panic. This skill is the triage decision tree.

The five incident types

Symptom Most likely cause First action Fix time
Reply rate dropped sharply Deliverability — emails in spam Run spam placement test 1-14 days
Bounce rate spiked >3% Bad list OR domain reputation Check bounce types 1-3 days
Domain blacklisted Shared IP bad actor OR your domain got flagged Check blacklists, rotate if needed 7-30 days
Inbox blocked in warmup Warmup network flagged sending patterns Pause, investigate, maybe replace 1-7 days
Gmail marking as promotional Content triggers (links, images, HTML) Simplify content 1-3 days

Decision tree: "my reply rate dropped"

Step 1: Quantify the drop

Was this week's reply rate < 50% of last 4 weeks' average?
  Yes → real drop, continue triage
  No  → noise, wait another week

If drop is real:

Step 2: Is it campaign-specific or fleet-wide?

Are ALL campaigns dropping, or just one?
  All → fleet-level issue (infrastructure or copy pattern)
  One → campaign-specific (targeting, copy, list)

Step 3: Fleet-wide drop — check these in order

  1. Smartlead Smart Delivery spam test (/email-deliverability-audit → run-spam-test.ts)

    • If inbox placement <70% → real deliverability issue, skip to Step 4
    • If inbox placement >85% → deliverability is fine, look at copy/targeting instead
  2. Check domain authentication (/email-deliverability-audit → check-domain-auth.ts)

    • Missing DKIM on any domain → fix immediately (see /zapmail-domain-setup-public for reconnect steps)
    • DMARC policy=reject with alignment failures → temporarily lower to quarantine
  3. Check warmup status (/smartlead-inbox-manager → list-health.ts)

    • If multiple inboxes blocked in warmup → warmup network flagged you
    • If reputation dropped "good" → "fair" on many inboxes → slow down sending volume

Read the full file on GitHub · 210 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. 2mo ago First seen · 210 lines · 83 tokens per session scan A c47d82b98c35

Subscribe to this mod's changes

deliverability-incident-response is a skill published in the GitHub repository AlexisMarasigan/coldoutboundskills (5 stars, last pushed 6mo ago), licensed MIT. It adds 83 tokens to every session and 2,308 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to deliverability-incident-response, differing in 92 lines, and is treated as a copy.

Related

deliverability-incident-response compared with skills from other repositories

deliverability-incident-response next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
deliverability-incident-responseAlexisMarasigan/coldoutboundskillsSkill56mo agoMITA83Claude Code
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143ktodayMITA103Claude Code