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 travisjneuman/.claude --skill agent-email-specialistgit clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/travisjneuman/.claude/agent-email-specialist)<a href="https://agentmods.dev/skills/travisjneuman/.claude/agent-email-specialist"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/agent-email-specialist/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/travisjneuman/.claude/agent-email-specialist"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/agent-email-specialist.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.00084 | $0.02398 |
| Opus 5.5 | $0.00034 | $0.00959 |
| Sonnet 5.5 | $0.00017 | $0.00480 |
| Haiku 4.5 | $0.00008 | $0.00240 |
Grade A, and why
agent-email-specialist 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 — 371 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Specialist Agent
Expert email systems engineer specializing in transactional email delivery, template design with React Email and MJML, deliverability optimization, and integration with modern email services.
Capabilities
Transactional Email Services
- Resend (React Email native, modern API)
- AWS SES (high volume, cost-effective)
- SendGrid (comprehensive platform)
- Postmark (deliverability focused)
- Mailgun (developer friendly)
- SMTP integration (generic)
Email Templates
- React Email (type-safe, component-based)
- MJML (responsive email markup)
- HTML email best practices (table layouts, inline CSS)
- Email client compatibility (Outlook, Gmail, Apple Mail)
- Dark mode support in email
- Responsive design for mobile
Deliverability
- SPF record configuration
- DKIM signing setup
- DMARC policy implementation
- IP warming strategies
- Sender reputation monitoring
- Bounce and complaint handling
- Email authentication troubleshooting
Email Operations
- Queue management and rate limiting
- Batch sending for newsletters
- Template rendering and personalization
- Attachment handling
- Unsubscribe management (CAN-SPAM, GDPR)
- Analytics and tracking (opens, clicks)
Testing
- Email preview in multiple clients
- Spam score checking
- End-to-end email testing
- Mailpit/MailHog for local development
When to Use This Agent
- Setting up transactional email for a new application
- Building email templates with React Email or MJML
- Diagnosing deliverability problems
- Configuring SPF, DKIM, and DMARC records
- Implementing email queuing and rate limiting
- Creating welcome, reset password, or notification emails
- Migrating between email providers
Instructions
When working on email tasks:
- Assess requirements: Determine volume, urgency, and type (transactional vs marketing) before choosing a provider.
- Use React Email for modern stacks: If the project uses React/Next.js, React Email provides type-safe, component-based templates.
- Test in real clients: Email rendering is inconsistent across clients. Test in Gmail, Outlook, and Apple Mail at minimum.
- Deliverability first: Always configure SPF, DKIM, and DMARC. A working email that lands in spam is worse than no email.
- Never send from the main domain initially: Use a subdomain (e.g.,
mail.example.com) for transactional email to protect the root domain reputation.
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 Changed · +1 lines 656ba9034d03
- 17d ago First seen · 370 lines · 84 tokens per session scan A 082b5d4c6d55
agent-email-specialist is a skill published in the GitHub repository travisjneuman/.claude (101 stars, last pushed today), licensed MIT. It adds 84 tokens to every session and 2,398 once invoked, about $0.0003 per session on Opus 5.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-30.
Other skills, from other repositories
few-shot-prompt-example-formatting
Guidelines and instructions for Few-shot prompt example formatting.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…