add-email-template

add-email-template is a command for Claude Code from mentilead/shopify-app-skill. It costs 0 tokens per session (466 once invoked), scanned A, original, MIT.

A command for adding an email template to a Shopify app's email system. It defines the template, its variables, HTML, queued delivery through Amazon SQS, background processing by an AWS Lambda worker, and suppression-list checks.

In plain words
What is it for?
Use it to add emails such as application approvals or weekly digests, including their dynamic fields, HTML layout, queueing, and worker support.
Why use it?
It keeps email work out of request handlers and provides a defined path for preventing messages to recipients who should not receive them.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: reads .claude/ paths.

Part of the shopify-app-skill plugin — 1 skill, 10 commands shipped together

Good fit Use it to add emails such as application approvals or weekly digests, including their dynamic fields, HTML layout, queueing, and worker support.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/mentilead/shopify-app-skill/add-email-template
Install

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.

Clone the repo
git clone --depth 1 https://github.com/mentilead/shopify-app-skill

Made for: Claude Code.

Or install shopify-app-skill, the plugin that ships this one along with the rest of its 1 skill, 10 commands.

Wrote 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.

agentmods badge for add-email-template

README.md
[![agentmods](https://agentmods.dev/badge/commands/mentilead/shopify-app-skill/add-email-template.svg)](https://agentmods.dev/commands/mentilead/shopify-app-skill/add-email-template)
Your own site
<a href="https://agentmods.dev/commands/mentilead/shopify-app-skill/add-email-template"><img src="https://agentmods.dev/badge/commands/mentilead/shopify-app-skill/add-email-template.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 466 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00466
Opus 5 $0.00000 $0.00233
Sonnet 5 $0.00000 $0.00093
Haiku 4.5 $0.00000 $0.00047

Measured 8d ago against content hash 858e74f6129d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

add-email-template 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 8d 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.

commands/add-email-template.md · 35 lines

How it starts

The opening of the file, as written. The whole thing — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Add Email Template

Create a new email template with SQS queuing, Lambda worker processing, and suppression list checking.

Arguments

$ARGUMENTS = template name and purpose (e.g., "application_approved for notifying applicants", "weekly_digest")

Instructions

  1. Parse the template name and purpose from $ARGUMENTS. If empty, ask the user what email to create and when it should be sent.
  2. Read .claude/skills/shopify-app/references/email-patterns.md for SQS queuing, suppression lists, and worker patterns.
  3. Read .claude/skills/shopify-app/references/lambda-architecture.md for SQS worker handler patterns.
  4. Create or update the email template definition:
    • Add the template type to the email types (e.g., in an enum or constant map)
    • Define the required template variables (recipient, subject line, dynamic fields)
    • Create the HTML template (inline CSS only — email clients strip <style> tags inconsistently)
  5. Add the SQS queue send helper in the relevant service function:
    • Queue via SendMessageCommand with templateType, recipientEmail, shopDomain, and variables
    • Never send email inline in request handlers — always queue
  6. Update the email worker Lambda (app/lambda-workers/email-worker.ts or similar):
    • Add a case for the new template type
    • Check the suppression list before sending
    • Render the template with variables
    • Send via Resend (or configured provider)
    • Log success/failure with structured logging
  7. If the email needs new DynamoDB storage (e.g., custom templates per shop):
    • Read .claude/skills/shopify-app/references/dynamodb-patterns.md
    • Add keys to app/services/dynamodb/keys.ts using the EMAIL_TEMPLATE#<type> pattern
  8. Create a unit test for the template rendering logic.
  9. Remind the user to:
    • Test with a real email address in the dev environment
    • Verify the SQS dead letter queue is configured for failed sends
    • Check the email renders correctly in major clients (Gmail, Outlook, Apple Mail)

Read the full file on GitHub · 35 lines

Changes

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.

  1. 8d ago First seen · 35 lines · 0 tokens per session scan A 858e74f6129d

Subscribe to this mod's changes

add-email-template is a command published in the GitHub repository mentilead/shopify-app-skill (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 466 tokens. 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.