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 inbox-lifecycle-managergit 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/inbox-lifecycle-manager)<a href="https://agentmods.dev/skills/growthenginenowoslawski/coldoutboundskills/inbox-lifecycle-manager"><img src="https://agentmods.dev/badge/skills/growthenginenowoslawski/coldoutboundskills/inbox-lifecycle-manager/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/inbox-lifecycle-manager"><img src="https://agentmods.dev/badge/skills/growthenginenowoslawski/coldoutboundskills/inbox-lifecycle-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00112 | $0.05000 |
| Opus 5.5 | $0.00045 | $0.02000 |
| Sonnet 5.5 | $0.00022 | $0.01000 |
| Haiku 4.5 | $0.00011 | $0.00500 |
Grade A, and why
inbox-lifecycle-manager 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 19d 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.
How it starts
The opening of the file, as written. The whole thing — 373 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inbox Lifecycle Manager
Diagnosis tells you a domain is sick. This skill decides whether it dies.
Every cold email fleet leaks money in two directions at once: you keep paying for burned domains that will never reply again, and you run under your send goal because nobody promoted the warmed reserves sitting idle. This is the weekly loop that fixes both, with an approval gate in the middle so nothing gets cancelled on a hunch.
Read-only by default. The plan step writes nothing, anywhere. Only the apply step, run after an explicit human "yes", changes a tag, a campaign, or a provider subscription.
When to use
- The weekly hygiene routine (Friday morning is the natural slot — see
/cold-email-weekly-rhythm) - "Which inboxes should I cancel?" / "What's burned?" / "Clean up my domains"
- "I'm under my daily send goal" / "How many domains do I need to buy?"
- "My inbox bill is too high" — the spend section prices every domain against what it earns
- After
/email-deliverability-auditor/deliverability-incident-responsehands you aSENDER_BURNEDverdict and you need to act on it
Not this skill: why a domain is bad (/email-deliverability-audit), fixing DNS
(/zapmail-domain-setup-public), an acute incident (/deliverability-incident-response),
warmup settings and signatures (/smartlead-inbox-manager).
The status model
Four statuses, and they apply to a whole domain, never to one inbox inside it.
| Status | Meaning | Warmup | In campaigns |
|---|---|---|---|
| Warmup | Newly provisioned, under 14 days of warmup | ON | no |
| Insurance | Warmed, healthy, idle — the reserve pool | ON | no |
| Active | Sending in live campaigns | OFF or minimal | yes |
| Cancel | Condemned; stop sending, cancel the subscription | OFF | no |
⛔ Never split a domain's inboxes across statuses. Mailbox providers judge reputation at the domain level. Half a domain "Active" and half "Cancel" means you are still sending from a domain you have declared burned, and the healthy half inherits the reputation of the dead half. Every decision below is computed per domain and applied to every inbox on it.
What ships with it
5 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.
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.
- 19d ago Changed · +32 lines 54a06c81884c
- 25d ago First seen · 341 lines · 112 tokens per session scan A 9db694689abd
inbox-lifecycle-manager is a skill published in the GitHub repository growthenginenowoslawski/coldoutboundskills (781 stars, last pushed 19d ago), licensed MIT. It adds 112 tokens to every session and 5,000 once invoked, about $0.0004 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-09-30.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.