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 realjaymes/marketingagentskills --skill lifecycle-marketing-campaignsgit clone --depth 1 https://github.com/realjaymes/marketingagentskillsWrote 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/realjaymes/marketingagentskills/lifecycle-marketing-campaigns)<a href="https://agentmods.dev/skills/realjaymes/marketingagentskills/lifecycle-marketing-campaigns"><img src="https://agentmods.dev/badge/skills/realjaymes/marketingagentskills/lifecycle-marketing-campaigns/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/realjaymes/marketingagentskills/lifecycle-marketing-campaigns"><img src="https://agentmods.dev/badge/skills/realjaymes/marketingagentskills/lifecycle-marketing-campaigns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
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 →
- low Excessive Agency · line 98 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00060 | $0.00853 |
| Opus 5 | $0.00030 | $0.00426 |
| Sonnet 5 | $0.00012 | $0.00171 |
| Haiku 4.5 | $0.00006 | $0.00085 |
Grade A, and why
lifecycle-marketing-campaigns 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 13d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lifecycle Marketing Campaigns Assistant
Design structured communication flows that guide prospects and customers through key journey stages.
When to Use
- User wants to create email sequences for different user segments
- User mentions: lifecycle campaigns, drip campaigns, onboarding emails, upgrade campaigns, retention flows, win-back campaigns
- User needs segment-specific messaging strategies
Business Types
SaaS: Activation, plan upgrades, feature adoption, renewals Digital Products: Free to paid conversion, course completion, repeat purchases, memberships Service Businesses: Lead nurturing, client onboarding, value delivery, expansion, referrals
Instructions
- Identify business type: SaaS, digital product, or service business
- Define segment: Free user, trial user, paid user, churned, etc.
- Set campaign goals: 2-3 specific objectives
- Design campaign flow: Day-by-day messaging plan
- Specify channels: Email, in-app, SMS, etc.
Campaign Flow Structure
For each campaign, output:
## Segment: [Segment Name]
**Campaign Goals:**
- [Goal 1]
- [Goal 2]
- [Goal 3]
**Campaign Flow:**
| Day | Messaging Focus | Description | CTA |
|-----|-----------------|-------------|-----|
| Day 0 | [Focus] | [Description] | "[CTA Text]" |
| Day 3 | [Focus] | [Description] | "[CTA Text]" |
SaaS Segments
Free Plan User
Goals: First action within 3 days, team invites, convert to paid within 14 days
| Day | Focus | Description |
|---|---|---|
| Day 0 | Welcome & Quick Start | Setup guide, highlight ease |
| Day 2 | Collaboration Value | Benefits of inviting teammates |
| Day 5 | Limit Awareness | Showcase free plan limits |
| Day 8 | Feature Spotlight | Highlight integrations |
| Day 12 | Case Study | Success story |
| Day 14 | Final Reminder | Urgency, what they lose |
Trial User
Goals: Drive feature adoption, build urgency, convert before expiration
Paid User
Goals: Consistent use, habit loops, drive upgrade to next tier
What ships with it
1 file 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.
- 13d ago First seen · 124 lines · 60 tokens per session scan A c8e208f824e9
lifecycle-marketing-campaigns is a skill published in the GitHub repository realjaymes/marketingagentskills (60 stars, last pushed 3d ago), licensed MIT. It adds 60 tokens to every session and 853 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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.
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…
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…