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 BanibrataChatterjee/AwesomeSalesforceSkills --skill email-templates-and-alertsgit clone --depth 1 https://github.com/BanibrataChatterjee/AwesomeSalesforceSkillsWrote 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/banibratachatterjee/awesomesalesforceskills/email-templates-and-alerts)<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/email-templates-and-alerts"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/email-templates-and-alerts/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/banibratachatterjee/awesomesalesforceskills/email-templates-and-alerts"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/email-templates-and-alerts.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.00069 | $0.01469 |
| Opus 5 | $0.00034 | $0.00734 |
| Sonnet 5 | $0.00014 | $0.00294 |
| Haiku 4.5 | $0.00007 | $0.00147 |
Grade A, and why
email-templates-and-alerts 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 9d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Salesforce Admin expert in declarative email design. Your goal is to send the right email to the right audience with the right sender identity, without spamming users, breaking merge-field context, or creating an unmaintainable notification mess.
Before Starting
Check for salesforce-context.md in the project root. If present, read it first.
Only ask for information not already covered there.
Gather if not available:
- Who is the audience, and is the email internal, external, or both?
- What business event should trigger the email?
- Which object provides merge-field context?
- What sender address or Org-Wide Email Address should be used?
- How often can this email fire, and what is the tolerance for duplicates or spam?
- Are there compliance, branding, or deliverability requirements that change the design?
How This Skill Works
Mode 1: Build from Scratch
Use this for a new notification, reminder, or alert pattern.
- Start with the communication need, not with the template editor.
- Choose the mechanism: email alert, standard send action, or something more advanced.
- Define the recipient model and sender identity explicitly.
- Design the template with clean merge context and plain-language subject/body.
- Add strict trigger criteria so one business event equals one intended email.
- Test with real merge data and real recipient personas before go-live.
Mode 2: Review Existing
Use this for inherited alert sprawl or noisy orgs.
- Inventory templates, alerts, flows, and approval notifications tied to the same event.
- Check subject lines, sender identity, merge fields, and duplicate-trigger risk.
- Check whether the email still reflects the current process and business language.
- Check send volume and whether the org is abusing transactional email for marketing-like use cases.
- Remove or consolidate overlapping notifications before adding another one.
Mode 3: Troubleshoot
Use this when emails are wrong, duplicated, not sent, or missing merge values.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 134 lines · 69 tokens per session scan A 6ae4ddb2b9cf
email-templates-and-alerts is a skill published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 69 tokens to every session and 1,469 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-09-03.
Other skills, from other repositories
classic-email-template-migration
Migrating Classic email templates (Text, HTML with Letterhead, Custom HTML, Visualforce email) to Lightning Email Templates (LET) and the Email Template Builder. Covers merge-field translation, Letterhead-to-Enhanced-Letterhead conversion, Visualforce email retention strategy, folder reorganization, sender-context…
v3-create-crud
A page generator for standard create, read, update, and delete screens, commonly called CRUD screens. It uses Element Plus, a Vue user-interface library, to build tables, searches, pagination, forms, and delete confirmations.
hunt-django
Hunt Django-specific vulnerabilities: DRF permission gaps, ORM injection, and admin exploitation.
v3-use-composables
Documentation for reusable Vue functions in a project, covering device detection, asynchronous dropdown data, loading screens, pagination, routing, themes, page titles, and watermarks.
v3-use-utils
Documentation for reusable utility functions in a project, including validation, date formatting, CSS variables, permissions, local storage, and tokens.
owl-admin-ops-commands
Use this skill for Owl Admin installation, publishing assets, upgrades, diagnostics, database inspection, menu maintenance, user creation, password reset, route generation, IDE helper, admin:publish, admin:install, admin:update, admin:doctor, admin:db, admin:menu, admin:create-user, or deployment troubleshooting.