deliverability-incident-response

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

A troubleshooting playbook for cold-email delivery problems, such as messages going to spam, bounced emails, blocked inboxes, or a drop in replies. It uses decision trees to connect symptoms with likely causes and next checks.

In plain words
What is it for?
Use it to investigate spam placement, rising bounce rates, blacklisted domains, blocked warm-up inboxes, Gmail promotional classification, and falling reply rates.
Why use it?
It gives a structured response when email performance suddenly changes, instead of relying on guesswork. It helps separate list problems, domain reputation issues, sending-pattern issues, and message-content issues.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: positional $N argument.

Good fit Use it to investigate spam placement, rising bounce rates, blacklisted domains, blocked warm-up inboxes, Gmail promotional classification, and falling reply rates.

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

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 deliverability-incident-response

README.md
[![agentmods](https://agentmods.dev/badge/skills/growthenginenowoslawski/coldoutboundskills/deliverability-incident-response/github.svg)](https://agentmods.dev/skills/growthenginenowoslawski/coldoutboundskills/deliverability-incident-response)
Your own site
<a href="https://agentmods.dev/skills/growthenginenowoslawski/coldoutboundskills/deliverability-incident-response"><img src="https://agentmods.dev/badge/skills/growthenginenowoslawski/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/growthenginenowoslawski/coldoutboundskills/deliverability-incident-response"><img src="https://agentmods.dev/badge/skills/growthenginenowoslawski/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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium MCP Rug Pull · line 141
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 144
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
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.00083 $0.02308
Opus 5 $0.00042 $0.01154
Sonnet 5 $0.00017 $0.00462
Haiku 4.5 $0.00008 $0.00231

Measured 12d ago against content hash c47d82b98c35, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, 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 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

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-auditrun-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-auditcheck-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-managerlist-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. 12d 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 growthenginenowoslawski/coldoutboundskills (702 stars, last pushed 25d ago), licensed MIT. It adds 83 tokens to every session and 2,308 once invoked, about $0.0004 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

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

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 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