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 agentmods add skills/mtnyilmaz/agents/email-developernpx skills add mtnyilmaz/agents --skill email-developergit clone --depth 1 https://github.com/mtnyilmaz/agentsWhat 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 | $0.00061 | $0.02652 |
| Opus 5 | $0.00030 | $0.01326 |
| Sonnet 5 | $0.00012 | $0.00530 |
| Haiku 4.5 | $0.00006 | $0.00265 |
Grade A, and why
email-developer 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 2d 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 — 357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Developer
Expert in building cross-client compatible, deliverable HTML email templates. Supports all three major email template frameworks: React Email, MJML, and Maizzle.
How to Choose a Framework
| Situation | Use |
|---|---|
| TypeScript/React codebase, transactional emails | React Email |
| Standalone email repo, TypeScript team, strong component model | React Email |
| Complex marketing/newsletter campaigns, HTML-first team | MJML |
| Design-system driven, Tailwind already in use, large template library | Maizzle |
| Non-technical team edits templates | MJML or Maizzle (no JSX) |
Detect from package.json:
@react-email/components→ React Email projectmjml→ MJML project@maizzle/framework→ Maizzle project
Reference Rules
Load these rules for the relevant context:
.agents/layers/concern/email/fundamentals.md— shared HTML email rules (inline styles, 600px, compliance — applies to all frameworks).agents/layers/framework/email/react/patterns.md— React Email components and patterns.agents/layers/framework/email/mjml/patterns.md— MJML XML syntax, partials, build pipeline.agents/layers/framework/email/maizzle/patterns.md— Maizzle Tailwind + Handlebars patterns.agents/layers/concern/email/deliverability.md— deliverability, compliance, infrastructure.agents/layers/universal/security-baseline.md— security requirements
Tech Stack (2026)
| Tool | Use case |
|---|---|
| React Email | Transactional emails in TypeScript codebase |
| MJML | Marketing / newsletter templates (XML → HTML) |
| Maizzle | Tailwind-based template system (Handlebars + Vite) |
| Resend | Primary sending provider (best DX, React Email native) |
| Postmark | Transactional-only (high deliverability) |
| SendGrid / Brevo | High-volume bulk / marketing campaigns |
| Email on Acid | Cross-client visual regression testing |
| mail-tester.com | Spam score testing |
What ships with it
1 file 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.
- 2d ago First seen · 357 lines · 61 tokens per session scan A 36c71275cc89
email-developer is a skill published in the GitHub repository mtnyilmaz/agents (6 stars, last pushed 3mo ago), licensed MIT. It adds 61 tokens to every session and 2,652 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…