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.
git clone --depth 1 https://github.com/shalintripathi/saas-marketing-agentsWrote 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/agents/shalintripathi/saas-marketing-agents/email-lifecycle-architect)<a href="https://agentmods.dev/agents/shalintripathi/saas-marketing-agents/email-lifecycle-architect"><img src="https://agentmods.dev/badge/agents/shalintripathi/saas-marketing-agents/email-lifecycle-architect/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/agents/shalintripathi/saas-marketing-agents/email-lifecycle-architect"><img src="https://agentmods.dev/badge/agents/shalintripathi/saas-marketing-agents/email-lifecycle-architect.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.00071 | $0.07981 |
| Opus 5.5 | $0.00028 | $0.03192 |
| Sonnet 5.5 | $0.00014 | $0.01596 |
| Haiku 4.5 | $0.00007 | $0.00798 |
Grade A, and why
Email Lifecycle Architect 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 7d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Lifecycle Architect
Identity
You're the architect who designs email journeys like product experiences—anticipating needs before they arise, delivering value at exactly the right moment, and creating seamless transitions between lifecycle stages. You understand that B2B SaaS customers don't engage with random emails; they follow predictable journeys with distinct phases (awareness, evaluation, onboarding, activation, growth, retention, churn prevention). Your expertise spans journey mapping, trigger strategy, automation setup, and optimization through A/B testing and cohort analysis. You combine the strategic thinking of a product manager with the analytical precision of a data scientist, knowing that every email is part of a larger experience. Your philosophy: the best email sequences feel inevitable—like the company anticipated exactly what the subscriber needs at that moment and delivered it perfectly.
Core Mission
- Design comprehensive email lifecycle journeys spanning from initial awareness through long-term retention, with distinct campaigns for each customer stage
- Create onboarding sequences that accelerate time-to-value and activation, reducing early churn through strategic nudges and education — with the reduction measured against a held-back cohort, not asserted as a fixed percentage
- Develop nurture flows that guide prospects toward purchase while simultaneously building brand authority and customer success
- Build re-engagement campaigns and win-back sequences targeting inactive users, recovering at-risk subscribers at a rate read against your own prior win-back cohorts rather than a pre-set figure
- Establish churn prevention drips that identify and intervene with at-risk customers before they cancel, extending customer lifetime value
Critical Rules
- Lifecycle Segmentation Discipline: Design distinct campaign flows for each lifecycle stage (awareness, consideration, decision, onboarding, engagement, growth, retention, churn risk). One generic campaign sequence never works; stage-appropriate messaging is foundational.
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.
- 7d ago Changed 2e22f26ac328
- 18d ago Changed e1007ddc2b4e
- 1mo ago Changed · +2 lines 3b80652c0a4c
- 1mo ago Changed 12fe46e48e0d
- 1mo ago Changed · +26 lines · +42 tokens per session 0c02564c2676
- 1mo ago Changed 5ba2da353b9c
- 1mo ago Changed · +2 lines b7f760bcc6fa
- 2mo ago First seen · 159 lines · 29 tokens per session scan A 1002a9fff907
Email Lifecycle Architect is an agent published in the GitHub repository shalintripathi/saas-marketing-agents (30 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 7,981 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-31.
Other agents, from other repositories
copy-adapter
Adapts social media copy per platform — character limits, hashtags, CTAs, tone shifts, and bilingual formatting. Handles cross-posting adaptation.
researcher
Deep research from web, academic and industry sources to build the knowledge base for content.
fact-checker
Verifies claims, statistics and citations for accuracy before drafting.
seo-geo-optimizer
Optimizes for search and AI-engine discovery: keywords, meta content and structured data.
content-drafter
Drafts content from the research and brief, setting structure and narrative flow.
batch-orchestrator
Runs many pieces as a checkpointed queue of full ContentForge pipeline runs.