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.
npx skills add growthenginenowoslawski/coldoutboundskills --skill deliverability-incident-responsegit clone --depth 1 https://github.com/growthenginenowoslawski/coldoutboundskillsWrote 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.
[](https://agentmods.dev/skills/growthenginenowoslawski/coldoutboundskills/deliverability-incident-response)<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.
<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>- NVIDIA SkillSpector warn
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]
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00083 | $0.03668 |
| Opus 5.5 | $0.00033 | $0.01467 |
| Sonnet 5.5 | $0.00017 | $0.00734 |
| Haiku 4.5 | $0.00008 | $0.00367 |
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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- deliverability-incident-response — 100% identical, 92 lines differ
How it starts
The opening of the file, as written. The whole thing — 282 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
-
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
-
Check domain authentication (
/email-deliverability-audit→check-domain-auth.ts)- Missing DKIM on any domain → fix immediately (see
/zapmail-domain-setup-publicfor reconnect steps) - DMARC policy=reject with alignment failures → temporarily lower to quarantine
- Missing DKIM on any domain → fix immediately (see
-
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
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.
- 1mo ago Changed · +72 lines 88c28db2b8a8
- 2mo ago First seen · 210 lines · 83 tokens per session scan A c47d82b98c35
deliverability-incident-response is a skill published in the GitHub repository growthenginenowoslawski/coldoutboundskills (802 stars, last pushed 1mo ago), licensed MIT. It adds 83 tokens to every session and 3,668 once invoked, about $0.0003 per session on Opus 5.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.
deliverability-incident-response compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| deliverability-incident-responsegrowthenginenowoslawski/coldoutboundskills | Skill | 802 | 1mo ago | MIT | A | 83 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 133k | today | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |
| chat-pet-sprite-creationmicrosoft/vscode | Skill | 195k | today | MIT | A | 53 | Claude Code, Codex |