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 NickCrew/Claude-Cortex --skill email-draftergit clone --depth 1 https://github.com/NickCrew/Claude-CortexWrote 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/nickcrew/claude-cortex/email-drafter)<a href="https://agentmods.dev/skills/nickcrew/claude-cortex/email-drafter"><img src="https://agentmods.dev/badge/skills/nickcrew/claude-cortex/email-drafter.svg" alt="Measured on agentmods" 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.00082 | $0.02231 |
| Opus 5 | $0.00041 | $0.01115 |
| Sonnet 5 | $0.00016 | $0.00446 |
| Haiku 4.5 | $0.00008 | $0.00223 |
Grade A, and why
email-drafter 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Drafter
Overview
This skill produces clear, purposeful emails calibrated to the right tone, length, and structure for the situation—whether you're reaching out cold to a potential partner, nudging a slow-to-respond client, or delivering difficult feedback to a colleague. It applies proven subject line formulas, places calls to action where they land hardest, and keeps emails as short as they need to be and no shorter. The goal is emails that get opened, read, and acted on.
When to Use
- Cold outreach to prospects, journalists, collaborators, or employers
- Follow-up emails after meetings, proposals, or no-reply situations
- Internal communication: project updates, feedback, requests
- Client-facing messages: onboarding, status updates, difficult news
- Professional introduction or networking emails
- Declining requests or delivering bad news diplomatically
- Responding to complaints or sensitive situations
When NOT to Use
- Bulk email marketing sequences (use
copywriterskill for campaign copy) - Legal notices, contracts, or compliance communications requiring specific phrasing
- Transactional system emails (order confirmations, password resets)
- Personal/casual texts or messages to close friends
Quick Reference
| Task | Approach |
|---|---|
| Subject line | Keep under 50 chars; use personalization, numbers, or questions |
| Formal tone | Full sentences, no contractions, "Dear [Name]", sign with full name |
| Casual tone | Contractions ok, first name greeting, conversational sign-off |
| Length | Cold email: 75–125 words; follow-up: 50–75 words; detailed request: up to 200 words |
| CTA | One CTA per email; make it specific and low-friction |
| Reply email | Acknowledge their last point before making your ask |
| Opener | Never start with "I hope this finds you well" |
Instructions
- Clarify the email's single purpose. Every email should do exactly one thing: make an ask, share information, confirm something, or respond to something. If you have two asks, send two emails. Identify: who is the recipient, what is the relationship, and what is the single desired outcome?
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 · 209 lines · 82 tokens per session scan A 01bab78db169
email-drafter is a skill published in the GitHub repository NickCrew/Claude-Cortex (38 stars, last pushed 2mo ago), licensed MIT. It adds 82 tokens to every session and 2,231 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-09-03.
Other skills, from other repositories
email-drafting
Professional email drafting — structure, tone, and templates for common business contexts.
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…