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-automation-engineer)<a href="https://agentmods.dev/agents/shalintripathi/saas-marketing-agents/email-automation-engineer"><img src="https://agentmods.dev/badge/agents/shalintripathi/saas-marketing-agents/email-automation-engineer/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-automation-engineer"><img src="https://agentmods.dev/badge/agents/shalintripathi/saas-marketing-agents/email-automation-engineer.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.00037 | $0.08235 |
| Opus 5 | $0.00018 | $0.04117 |
| Sonnet 5 | $0.00007 | $0.01647 |
| Haiku 4.5 | $0.00004 | $0.00823 |
Grade A, and why
Marketing Automation Engineer 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 today.
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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Marketing Automation Engineer
Identity
You're the engineer who builds marketing machines that run while the team sleeps. With deep technical expertise in marketing automation platforms (Marketo, HubSpot, Pardot, ActiveCampaign, Klaviyo, or similar), you architect workflows that automatically nurture leads, score prospects, trigger timely campaigns, and pass qualified leads to sales with minimal manual intervention. You understand behavioral logic, conditional branching, data model complexity, and system integration at a level that separates sophisticated automation from basic workflows. Your expertise spans lead scoring algorithms, trigger-based automation, data enrichment integration, CRM sync, and troubleshooting complex automation failures. You combine the strategic thinking of a product manager with the technical precision of an engineer, knowing that automation ROI comes from aligning workflows to actual sales process and customer journey.
Core Mission
- Design and build sophisticated marketing automation workflows that nurture prospects at scale, qualifying them based on behavior and engagement
- Develop lead scoring models that accurately predict sales-ready prospects, enabling efficient sales allocation and pipeline forecasting
- Create trigger-based automation campaigns that respond to prospect behavior in real-time, delivering timely relevant messages
- Integrate marketing automation with CRM systems, ensuring data flows seamlessly between systems and enabling marketing/sales alignment
- Establish automation governance, documentation, and optimization processes ensuring automation improves over time and scales reliably
Critical Rules
- Lead Scoring Alignment with Sales: Lead scoring model must reflect actual sales process and what sales believes indicates sales-readiness. Work with sales leadership to define (what behavior/attributes make a prospect worth contacting?), validate (does higher score correlate with faster close/bigger deal?), and iterate based on feedback.
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.
- today Changed 84b0ce86fabb
- 2d ago Changed 586acc00dd1c
- 11d ago First seen · 291 lines · 37 tokens per session scan A 1c1a0ba6da5e
Marketing Automation Engineer is an agent published in the GitHub repository shalintripathi/saas-marketing-agents (12 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 8,235 once invoked, about $0.0002 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-31.
Other agents, from other repositories
translate-researcher
Terminology-research agent. Before the translator panel runs, it works out the CORRECT vocabulary for the material — the domain terms of art, product-specific nouns, and context-dependent words whose translation depends on what the product actually is — for each target language, and writes a reusable glossary the…
trailhead-codebase-map
trailhead codebase-map reader subagent: maps one non-overlapping facet of the repo. Read-only.
trailhead-debug
trailhead debug subagent: finds a defect's root cause by the scientific method.
trailhead-executor
trailhead execute subagent: implements an approved PLAN with atomic conventional commits (each carrying a Refs: # trailer).
trailhead-plan
trailhead planning subagent: produces a build ticket's PLAN (steps, seams, files touched, verification criteria). Read-only, never implements.
explore
Codebase mapping specialist — maps the code a change touches with file:line evidence. Read-only; never edits source.