Email Composer

Email Composer is a skill for Claude Code, Codex from Justdvp/claude-code-templates. It costs 31 tokens per session (1,527 once invoked), scanned A, original, MIT.

A guide for drafting professional emails for business, technical, or customer communication. It uses the purpose, recipient, key points, and desired tone to shape the message.

In plain words
What is it for?
Use it to write requests, follow-ups, announcements, and other professional emails. It can adapt the draft to relationships such as colleague, customer, manager, or vendor.
Why use it?
It removes the need to work out the email’s structure and wording from scratch. It helps turn brief context into a clear message with a subject, body, request, and sign-off.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Install

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.

agentmods
npx agentmods add skills/justdvp/claude-code-templates/email-composer
Any agent
npx skills add Justdvp/claude-code-templates --skill email-composer
Clone the repo
git clone --depth 1 https://github.com/Justdvp/claude-code-templates

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for Email Composer

README.md
[![agentmods](https://agentmods.dev/badge/skills/justdvp/claude-code-templates/email-composer.svg)](https://agentmods.dev/skills/justdvp/claude-code-templates/email-composer)
Your own site
<a href="https://agentmods.dev/skills/justdvp/claude-code-templates/email-composer"><img src="https://agentmods.dev/badge/skills/justdvp/claude-code-templates/email-composer.svg" alt="Measured on agentmods" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,527 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.01527
Opus 5 $0.00015 $0.00763
Sonnet 5 $0.00006 $0.00305
Haiku 4.5 $0.00003 $0.00153

Measured 5d ago against content hash fee7df66bbb4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

Email Composer 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 5d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

cli-tool/components/skills/enterprise-communication/email-composer/SKILL.md · 318 lines

How it starts

The opening of the file, as written. The whole thing — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Email Composer

Quick start

Provide context and purpose, and I'll draft an appropriate email.

What I need:

  • Purpose of email (request, follow-up, announcement, etc.)
  • Recipient relationship (colleague, customer, manager, vendor)
  • Key points to include
  • Desired tone (formal, casual, urgent, friendly)

Email structure

Standard professional email format:

Subject: [Clear, specific subject line]

[Greeting],

[Opening - context/purpose]

[Body - main points]

[Closing - call to action]

[Sign-off]
[Your name]

Common email types

Request for information

Subject: Question about Q4 project timeline

Hi [Name],

I hope this email finds you well. I'm reaching out regarding the Q4 product launch timeline.

Could you provide an update on:
- Current progress on feature development
- Expected completion date for testing phase
- Any blockers or dependencies we should be aware of

This will help us coordinate with the marketing team for the launch materials.

Thanks in advance for your help!

Best regards,
[Your name]

Follow-up email

Subject: Following up: Proposal for new payment system

Hi [Name],

I wanted to follow up on the payment system proposal I sent last week. I understand you're busy, so I wanted to make sure it didn't get lost in your inbox.

To recap, the proposed system would:
- Reduce transaction fees by 30%
- Integrate with existing accounting software
- Improve customer checkout experience

I'd be happy to schedule a brief call to discuss any questions you might have.

Looking forward to hearing from you.

Best,
[Your name]

Technical update

Subject: API Maintenance Window - [Date]

Team,

This is a reminder that we'll be performing scheduled maintenance on our API infrastructure on [Date] from [Time] to [Time] [Timezone].

During this window:
- API endpoints will be unavailable
- Database will be upgraded to v14
- SSL certificates will be renewed

Expected downtime: 2 hours

What you need to do:
- Notify your users of the planned downtime
- Ensure retry logic is in place for API calls
- Monitor your application after maintenance completes

If you have any concerns or conflicts with this schedule, please let me know by [Date].

Technical details available in our status page: [link]

Thanks,
[Your name]

Read the full file on GitHub · 318 lines

Changes

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.

  1. 5d ago First seen · 318 lines · 31 tokens per session scan A fee7df66bbb4

Subscribe to this mod's changes

Email Composer is a skill published in the GitHub repository Justdvp/claude-code-templates (7 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 1,527 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

agentic-delivery-playbook

Coding Agent Preflight for non-trivial coding work in Pi: classify direct/lightweight/full, lock goal/non-goals/risks/evidence, require approval when needed, and coordinate Pi goals/subagents with truthful routing. Use when ambiguity, risk, scope, or reviewability justifies a delivery contract; skip clear small direct…

arcayne/agentic-delivery-playbook · 77 tokens

running-a-pipeline

Run, resume, or list installed Superpipelines workflows from the registry.

gustavo-meilus/superpipelines · 20 tokens

sk-platform-dispatch

Resolves the active runtime tier and provides the canonical DISPATCH contract for all pipeline step execution. Use when an orchestrator skill needs to dispatch pipeline steps — performs tier detection, loads the platform profile, and executes the Tier 2 inline loop when no subagent primitive is available.

gustavo-meilus/superpipelines · 61 tokens

creating-a-pipeline

Design and scaffold a new named Superpipelines workflow after scope, brief, topology, audit, and human approval gates.

gustavo-meilus/superpipelines · 29 tokens

pipeline-architect-protocol

Loaded by the pipeline-architect agent to design or mutate Superpipelines pipeline topology and data-only CAD artifacts.

gustavo-meilus/superpipelines · 28 tokens

sk-pipeline-paths

Resolves scope-aware absolute file paths for Superpipelines artifacts across local, project, and user scopes. Use when creating or accessing agents, skills, support files, temporary directories, or the pipeline registry, given a known scope and pipeline name.

gustavo-meilus/superpipelines · 55 tokens