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 Misar-AI/misarmail-mcp --skill build-email-automationgit clone --depth 1 https://github.com/Misar-AI/misarmail-mcpWrote 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/misar-ai/misarmail-mcp/build-email-automation)<a href="https://agentmods.dev/skills/misar-ai/misarmail-mcp/build-email-automation"><img src="https://agentmods.dev/badge/skills/misar-ai/misarmail-mcp/build-email-automation/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/misar-ai/misarmail-mcp/build-email-automation"><img src="https://agentmods.dev/badge/skills/misar-ai/misarmail-mcp/build-email-automation.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.00050 | $0.00359 |
| Opus 5 | $0.00025 | $0.00179 |
| Sonnet 5 | $0.00010 | $0.00072 |
| Haiku 4.5 | $0.00005 | $0.00036 |
Grade A, and why
build-email-automation 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 11d 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.
What it actually says
Build an email automation
1. Check what already exists
list_automations first. Two automations on the same trigger will both fire,
and the contact receives duplicate mail — a failure users usually discover from
a complaint rather than from the dashboard.
2. Design before building
Choose a trigger: contact_created, tag_added, campaign_opened,
link_clicked, or date_based. Then lay out the steps with explicit delays
and explain each choice to the user.
Practical guidance worth stating:
- First email within an hour of the trigger; the rest spaced 2–4 days.
- Keep a welcome series to 3–5 emails. Longer sequences bleed unsubscribes.
- Include an exit condition (a tag applied on conversion) so a converted contact stops receiving the sequence.
3. Build it inactive
create_automation with active: false. Show the result via get_automation
and let the user read the steps back before anything can fire.
Only call toggle_automation with active: true after explicit confirmation.
Activating starts enrolling live contacts immediately.
Templates
list_templates and create_template — use {{variable}} placeholders and
preview substitution with render_template before wiring a template into a
step. An automation that ships Hi {{first_name}} to contacts with no first
name is a visible, embarrassing failure.
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.
- 11d ago First seen · 40 lines · 50 tokens per session scan A d3912f3896ae
build-email-automation is a skill published in the GitHub repository Misar-AI/misarmail-mcp (1 stars, last pushed 3d ago), licensed MIT. It adds 50 tokens to every session and 359 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-31.
Other skills, from other repositories
email-automation-builder
Build multi-sequence email automation flows with branching logic. Triggers on: "build email automation", "create email funnel", "email automation flow", "welcome series with branches", "conditional email sequence", "set up automation", "email workflow builder", "segmented email flow", "advanced email sequence"…
email-management-expert
Expert email management assistant for Apple Mail. Use this when the user mentions inbox management, email organization, email triage, inbox zero, organizing emails, managing mail folders, email productivity, checking emails, or email workflow optimization. Provides intelligent workflows and best practices for…
ai-newsletter
Use when building and monetizing AI-powered email newsletters. Curate content, automate writing, and grow paid subscriptions. Generate $1K-20K/month.
confirmation-protocol
Foresay-derived confirmation workflow for email operations. Use this skill BEFORE executing archive-mail with vague filters, composeemail (sending mail), deleteemail/moveemail in bulk, or any operation that touches 5+ emails. Show user a structured preview of "what I understood" before taking action, achieving…
bulk-operation-preview
Show structured preview of bulk email operations (5+ emails) before execute. Group by thread, flag false-positive candidates, count side-effect scope (files written, attachments downloaded, mailboxes touched). Use after email-search-disambiguation finishes Phase 1, as Phase 2 of the confirmation protocol.
email-search-disambiguation
A clarification step for email searches when a person, time period, direction, or scope is unclear. It presents specific possible meanings so the user can choose one.