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 eddiebelaval/squire --skill email-composergit clone --depth 1 https://github.com/eddiebelaval/squireWrote 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/eddiebelaval/squire/email-composer)<a href="https://agentmods.dev/skills/eddiebelaval/squire/email-composer"><img src="https://agentmods.dev/badge/skills/eddiebelaval/squire/email-composer.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00014 | $0.01589 |
| Opus 5 | $0.00007 | $0.00794 |
| Sonnet 5 | $0.00003 | $0.00318 |
| Haiku 4.5 | $0.00001 | $0.00159 |
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 4d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Composer
The Email Composer skill helps you craft professional, effective emails for any business context. Whether you need to reach out to a client, respond to a team inquiry, follow up on a meeting, or send a cold outreach message, this skill ensures your emails are clear, appropriately toned, and action-oriented.
This skill analyzes the context you provide and generates emails that match the appropriate level of formality, include necessary components (subject line, greeting, body, call-to-action, closing), and maintain professional standards. It can adapt tone from casual internal communications to formal external correspondence.
The skill also considers email best practices like brevity, clarity, scannable structure, and clear next steps to maximize response rates and effectiveness.
Core Workflows
Workflow 1: Draft New Email
- Gather Context: Understand the purpose, recipient, and key points
- Determine Tone: Assess formality level (casual, professional, formal)
- Structure Email: Create subject line, opening, body paragraphs, CTA, closing
- Review & Refine: Check for clarity, conciseness, and appropriate tone
- Deliver: Present complete email ready to send
Workflow 2: Reply to Email Thread
- Review Thread: Analyze previous messages for context
- Identify Key Points: Extract questions or items requiring response
- Craft Response: Address all points systematically
- Maintain Thread: Preserve relevant context while staying concise
- Close Loop: Ensure all items are addressed with clear next steps
Workflow 3: Email Template Creation
- Identify Use Case: Understand the recurring scenario
- Define Variables: Mark customizable sections
- Create Template: Build reusable structure
- Add Guidelines: Include usage notes and customization tips
- Test & Validate: Review with example content
Quick Reference
| Action | Command/Trigger |
|---|---|
| Draft new email | "Draft email to [recipient] about [topic]" |
| Reply to thread | "Write reply to [sender] addressing [points]" |
| Cold outreach | "Compose cold email to [prospect] for [purpose]" |
| Follow-up email | "Write follow-up on [topic] from [date/meeting]" |
| Thank you email | "Draft thank you email for [reason]" |
| Internal update | "Write team email about [update/announcement]" |
| Create template | "Create email template for [use case]" |
| Adjust tone | "Make this more [formal/casual/friendly]" |
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.
- 4d ago First seen · 176 lines · 14 tokens per session scan A 025281d2c4ef
Email Composer is a skill published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 22d ago), licensed MIT. It adds 14 tokens to every session and 1,589 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
Email Composer
Draft professional, well-structured emails for any business context.
novu-inbox-integration
Integrate Novu's in-app notification inbox into web applications. Supports React, Next.js, and vanilla JavaScript. Includes the Inbox component (bell icon + notification feed), composable components (Bell, Notifications, InboxContent, Preferences), headless hooks, branded theming, custom render props, multi-tenancy…
novu-design-workflow
Design notification workflows the Novu way — choose channels, set severity, decide when a workflow is critical, configure digests, and route based on subscriber state. Applies to BOTH dashboard-authored and code-first (@novu/framework) workflows. Use when planning a new workflow, deciding which channels to include…
human-cli
Reach the actual human you're working for via the human CLI (ask/approve/choose/tell) when you need a decision, approval, or notification and no one is watching this terminal right now. Use for background/autonomous/scheduled runs, risky or irreversible actions, and genuine multi-way ambiguity — not for routine…
novu-dashboard-workflows
Author step content for Novu workflows defined in the Dashboard or generated/edited via the Novu MCP. Use when filling in step controls (subject, body, editorType, headers, body, conditions) for email, in-app, sms, push, chat, delay, digest, throttle, or HTTP Request steps.
novu-manage-preferences
Configure notification preferences in Novu at the workflow and subscriber level. Set default channel preferences (email, SMS, push, chat, in-app), mark preferences as read-only or subscriber-editable, and manage subscriber-specific overrides. Use when setting up notification opt-in/opt-out, configuring per-channel…