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 KhaledSaeed18/dotclaude --skill email-draftgit clone --depth 1 https://github.com/KhaledSaeed18/dotclaudeWrote 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/khaledsaeed18/dotclaude/email-draft)<a href="https://agentmods.dev/skills/khaledsaeed18/dotclaude/email-draft"><img src="https://agentmods.dev/badge/skills/khaledsaeed18/dotclaude/email-draft/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/skills/khaledsaeed18/dotclaude/email-draft"><img src="https://agentmods.dev/badge/skills/khaledsaeed18/dotclaude/email-draft.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.00113 | $0.00836 |
| Opus 5.5 | $0.00045 | $0.00334 |
| Sonnet 5.5 | $0.00023 | $0.00167 |
| Haiku 4.5 | $0.00011 | $0.00084 |
Grade A, and why
email-draft 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 25d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The reader decides in the first two lines whether to act now, later, or never. Put the purpose and the ask there, make the ask easy to say yes to, and stop when the reader has what they need.
Before drafting
- Who is the reader, what do they already know, and what is their relationship to you (they owe you a reply, you are asking a favour, you are reporting up).
- What do you need: a decision, information, an action, an introduction, or nothing (an FYI). If more than one, split into separate messages or make one the ask and the rest optional.
- What would make the reply easy: a yes/no question, options with a recommendation, a date, a link to the thing.
Structure
Subject: <the content, specific> e.g. "Ethics form signature needed by Thu 25 Sep"
<Greeting matching the relationship>
<Line 1: why you are writing, in one sentence.>
<Line 2: the ask, with the date or the options.>
<Context: two to five sentences, only what the reader needs to decide. Numbers, links, attachments named.>
<Close: what happens next, thanks that is specific.>
<Sign-off and name>
For an FYI, say so in the subject ("FYI: ...") and keep it to three lines.
Register
- Supervisor or senior: respectful, direct, no hedging stacks; show you did the work before asking; offer options with your recommendation; propose a time rather than "whenever suits".
- Colleague or team: plain, short, first names; the ask in the first line.
- Open-source maintainer: lead with the issue or PR link, what you tried, what you observed, what you are asking; respect their time; no pressure.
- Support or vendor: account id, exact error, steps to reproduce, what you need; one issue per ticket.
- Recruiter or external: formal, complete sentences, one clear next step.
- Difficult messages (declining, disagreeing, chasing, correcting): state the position in the first line without apology or preamble, give the reason in one or two sentences, offer the alternative, keep the door open. Never argue the other person's motives.
- Chasing: reply in the same thread, restate the ask and the date, offer a smaller ask if the original was large.
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.
- 25d ago First seen · 56 lines · 113 tokens per session scan A 84082786b2f6
email-draft is a skill published in the GitHub repository KhaledSaeed18/dotclaude (5 stars, last pushed 2d ago), licensed MIT. It adds 113 tokens to every session and 836 once invoked, about $0.0005 per session on Opus 5.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-22.
Other skills, from other repositories
give-me-tips
Explains any senpi tip in depth, including Tip: lines in the TUI. Use when the user asks about a tip, what a tipped feature does, or which tips they can see.
knowledge-base-builder
FAQ identification from support tickets, step-by-step tutorial creation, screenshot/video script guidance, search optimization, and self-service deflection tracking.
skill-composer-studio
CHAIN multiple existing skills into custom multi-step workflows. Programmable skill combinations with automatic handoffs. Create composite skills from building blocks with conditional logic.
slack-message-formatter
Convert long text into Slack-optimized format with emojis, bullets, code blocks, and threading suggestions.
suede-onboarding
Suede-affiliated onboarding and activation strategy for first-run sequencing, empty states, setup checklists, activation milestones, time to value, and retention-linked measurement. Use when users sign up but fail to reach first value or the product needs a new first-session flow. NOT FOR: registration optimization…
cowork-calendar-defrag
Audit your calendar with Cowork's calendar tools -- measure meeting load and fragmentation, identify which recurring meetings earn their slot, propose consolidations and focus blocks, and draft the diplomatic messages that reclaim your week.