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/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/agents/travisjneuman/.claude/email-specialist)<a href="https://agentmods.dev/agents/travisjneuman/.claude/email-specialist"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/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/agents/travisjneuman/.claude/email-specialist"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/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.00077 | $0.02390 |
| Opus 5 | $0.00039 | $0.01195 |
| Sonnet 5 | $0.00015 | $0.00478 |
| Haiku 4.5 | $0.00008 | $0.00239 |
Grade A, and why
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 12d 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 — 379 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.
- 12d ago First seen · 379 lines · 77 tokens per session scan A 5762a4012ef7
email-specialist is an agent published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 6d ago), licensed MIT. It adds 77 tokens to every session and 2,390 once invoked, about $0.0004 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-30.
Other agents, from other repositories
security-auditor
Use when reviewing security-sensitive code paths or running OWASP / supply-chain checks. Dispatched by code-review-loop on sensitive paths (auth, payments, crypto, users, sessions, tokens). Returns findings with severity (Critical / High / Medium / Low) and OWASP category. Context: A diff touches the auth middleware.…
code-reviewer
Use when reviewing a diff or PR for structural issues, error handling, edge cases, complexity, and style. Dispatched primarily by code-review-loop. Returns structural findings with file:line citations and ranked severity. Pairs with security-auditor for sensitive paths. Context: A PR is ready for first-pass review.…
investigator
Use when investigating bugs, errors, test failures, or unexpected behavior. Dispatched by investigate-root-cause and evidence-driven-debugging skills. Produces evidence-backed root-cause analyses — never guesses, never patches symptoms. Context: An API endpoint is returning intermittent 500s. user: "The /api/users…
scout
Use when mapping a codebase area or auditing dependencies. Dispatched by the map-codebase and audit-dependencies skills. Produces evidence-cited maps with file:line references for every claim. Context: A teammate needs to know how the auth flow works. user: "Map the auth flow for me." assistant: "Dispatching the scout…
architect
Use when reviewing the architecture dimension of a written plan. Dispatched primarily by plan-review-architecture (via plan-review). Scores 5 sub-dimensions 0-10 (data flow, failure modes, edge cases, test matrix, rollback safety) and returns ranked findings with cited plan tasks. Context: A plan has been written and…
backend-expert-csk
Senior .NET backend expert. Applies the project's backend-pattern skill (devarch-module = MediatR CQRS / IResult / AOP by default; a project may declare its own). Use proactively — owns server behaviour: endpoints, handlers, validators, controllers, business rules, integrations. Any request about it is yours whatever…