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 adamjali/claude-skills --skill email-broadcastsgit clone --depth 1 https://github.com/adamjali/claude-skillsWrote 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/adamjali/claude-skills/email-broadcasts)<a href="https://agentmods.dev/skills/adamjali/claude-skills/email-broadcasts"><img src="https://agentmods.dev/badge/skills/adamjali/claude-skills/email-broadcasts/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/adamjali/claude-skills/email-broadcasts"><img src="https://agentmods.dev/badge/skills/adamjali/claude-skills/email-broadcasts.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.00102 | $0.01520 |
| Opus 5 | $0.00051 | $0.00760 |
| Sonnet 5 | $0.00020 | $0.00304 |
| Haiku 4.5 | $0.00010 | $0.00152 |
Grade A, and why
email-broadcasts 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 10d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Broadcasts
<execution_context>
- 🟢 Auto: contact/audience counts, history reads, knowledge lookups
- 🟡 ASK on: draft generation (preview required), test-segment send (still asks before the real send)
- 🔴 NEVER: send to the general audience without an explicit "yes send it" (or "schedule it for X")
- Mandatory self-preview: ALWAYS send a test broadcast to the test segment first, wait for "looks good"
- History: keep the last 5 broadcasts full, archive older to one-line at the bottom of
history.md</execution_context>
Setup (one time)
Fill in references/config.md (brand, from/reply-to, physical address for CAN-SPAM, audience
- test segment IDs, test recipients). Set:
export RESEND_API_KEY="your-key" # free key at https://resend.com
Manage contacts in your Resend Audience (import a CSV, or sync from your own source). This skill treats the Resend audience as the source of truth — no specific backend is assumed.
Routing — what does the user want?
| User says | Route to |
|---|---|
| "send/draft a broadcast", "announce", "newsletter" | → Draft & Send workflow |
| "how many contacts/subscribers" | → Resend: list contacts / audience count |
| "what have we sent", "email history" | → History |
| "open rate", "stats" | → Resend: list/get broadcast |
| "how does unsubscribe / CAN-SPAM work" | → Knowledge lookup (below) |
Draft & Send Workflow
What ships with it
3 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.
- 10d ago First seen · 150 lines · 102 tokens per session scan A d8e7a10b0b0f
email-broadcasts is a skill published in the GitHub repository adamjali/claude-skills (1 stars, last pushed 1mo ago), licensed MIT. It adds 102 tokens to every session and 1,520 once invoked, about $0.0005 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
branch-recap
Takes stock of what a branch actually changed, before it gets pushed — works out the scope itself, then lays the change out group by group in one pass: files touched, what was done and why, how, and what deserves a second look, quoting code only where a remark needs it rather than reprinting the diffs. Closes on a…
audit-context
Measures where a project's Claude context is going before applying any of clean-context's levers. Reports what Glob discovers with and without ignore files applied, the twenty largest files in the repo and which are generated, the cumulative size of every CLAUDE.md loaded for this working directory, and how many MCP…
slack-changelog
Turns what changed in a release into a Slack changelog a non-technical audience can read: filtered to what they would actually notice, one bullet per idea, plain language, no code vocabulary. Works out the scope itself across however many repositories sit in the working directory (a project can span several…
ignore-setup
Set up a project so Claude stops discovering lockfiles, generated code, minified assets and binaries on every search — a managed .ignore, the Glob setting that makes Glob obey it, and a short read-deny list for secrets. Use when someone asks for a .claudeignore, asks to exclude files from the context, says Claude…
plugin-commands
Commands for validating, testing, iterating on, and releasing plugins in this marketplace (claude-toolbelt) — plugin validate, watcher-parity check, eval, --plugin-dir dev loop, plugin tag. Use when validating a plugin before pushing, running skill evals, developing a plugin without touching the installed cache, or…
commit
Create a single well-crafted git commit from current changes. Analyzes diff, follows repo's commit style, and writes a concise "why not what" message.