What is modernize-email-templates?

A planning command for reviewing Salesforce email templates and their modernization path. It distinguishes Classic, Lightning, and Enhanced LEX templates and checks for Visualforce risks, merge-field problems, and attachment issues.

Inventory and classify email templates, validate merge fields, audit attachments, and produce a migration plan for a folder or org.

It shows which templates may need changes and why, without changing or deploying them. This helps plan work before templates that depend on older technology become harder to maintain.

modernize-email-templates — Command by BanibrataChatterjee

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/BanibrataChatterjee/AwesomeSalesforceSkills

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/modernize-email-templates/github.svg)](https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/modernize-email-templates)

Your own site

<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/modernize-email-templates"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/modernize-email-templates/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/modernize-email-templates"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/modernize-email-templates.svg" alt="Reviewed on agentmods" width="80" 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 249 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00249
Opus 5.5	$0.00000	$0.00100
Sonnet 5.5	$0.00000	$0.00050
Haiku 4.5	$0.00000	$0.00025

Measured 2mo ago against content hash 39912cb7c9d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

modernize-email-templates 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 2mo 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/modernize-email-templates.md · 36 lines

What it actually says

/modernize-email-templates — Audit and plan email template modernization

Wraps agents/email-template-modernizer/AGENT.md. Classifies Classic vs Lightning vs Enhanced LEX templates, flags Visualforce risks, produces migration plan.

Step 1 — Collect inputs

1. Scope?  folder:<DeveloperName>  OR  org
2. Target org alias?

Step 2 — Load the agent

Read agents/email-template-modernizer/AGENT.md + mandatory reads.

Step 3 — Execute the plan

Inventory templates, classify by engine, score each, merge-field validation, attachment audit, emit migration plan.

Step 4 — Deliver the output

Summary, classification table, per-template findings, migration plan, Process Observations, citations.

/build-flow for flows that reference deprecated templates
/analyze-field-impact for fields used only by soon-to-retire templates

What this command does NOT do

Does not modify or deploy templates.
Does not send test emails.
Does not migrate templates into Marketing Cloud / Account Engagement.

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.

2mo ago First seen · 36 lines · 0 tokens per session scan A 39912cb7c9d3

Subscribe to this mod's changes

modernize-email-templates is a command published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (4 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 249 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.

modernize-email-templates next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
modernize-email-templatesBanibrataChatterjee/AwesomeSalesforceSkills	Command	4	6mo ago	Apache-2.0	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	today	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	today	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	today	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	today	MIT	A	14	Claude Code