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/mentilead/shopify-app-skillWrote 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/commands/mentilead/shopify-app-skill/add-email-template)<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>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.00000 | $0.00466 |
| Opus 5 | $0.00000 | $0.00233 |
| Sonnet 5 | $0.00000 | $0.00093 |
| Haiku 4.5 | $0.00000 | $0.00047 |
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.
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
- Parse the template name and purpose from
$ARGUMENTS. If empty, ask the user what email to create and when it should be sent. - Read
.claude/skills/shopify-app/references/email-patterns.mdfor SQS queuing, suppression lists, and worker patterns. - Read
.claude/skills/shopify-app/references/lambda-architecture.mdfor SQS worker handler patterns. - 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)
- Add the SQS queue send helper in the relevant service function:
- Queue via
SendMessageCommandwithtemplateType,recipientEmail,shopDomain, andvariables - Never send email inline in request handlers — always queue
- Queue via
- Update the email worker Lambda (
app/lambda-workers/email-worker.tsor 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
- 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.tsusing theEMAIL_TEMPLATE#<type>pattern
- Read
- Create a unit test for the template rendering logic.
- 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)
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.
- 8d ago First seen · 35 lines · 0 tokens per session scan A 858e74f6129d
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.
Other commands, from other repositories
cloudflare-durable-objects:debug
Interactive Durable Objects debugging workflow. Diagnoses common DO errors, configuration issues, and runtime problems with step-by-step troubleshooting.
cloudflare-durable-objects:migrate
Interactive Durable Objects migration assistant. Guides through new class creation, renaming, deletion, and transfer migrations with validation.
cloudflare-durable-objects:optimize
Interactive Durable Objects performance optimization assistant. Analyzes existing DO code and provides specific optimization recommendations with implementation guidance.
cloudflare-durable-objects:patterns
Interactive Durable Objects pattern selection wizard. Helps choose the right DO pattern for your use case and generates implementation code with best practices.
cloudflare-durable-objects:setup
Interactive Durable Objects project initialization. Scaffolds new DO project with proper bindings, migrations, and boilerplate code.
cloudflare-queues:setup
Interactive wizard to set up Cloudflare Queues with queue creation, producer/consumer binding configuration, and Dead Letter Queue setup. Use when user wants to create first queue or add queues to existing Worker.