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/usejunior/email-agent-mcp/email-draftingnpx skills add UseJunior/email-agent-mcp --skill email-draftinggit clone --depth 1 https://github.com/UseJunior/email-agent-mcpWrote 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/usejunior/email-agent-mcp/email-drafting)<a href="https://agentmods.dev/skills/usejunior/email-agent-mcp/email-drafting"><img src="https://agentmods.dev/badge/skills/usejunior/email-agent-mcp/email-drafting.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 | $0.00084 | $0.01889 |
| Opus 5 | $0.00042 | $0.00945 |
| Sonnet 5 | $0.00017 | $0.00378 |
| Haiku 4.5 | $0.00008 | $0.00189 |
Grade A, and why
email-drafting 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.
How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Response Drafting
This skill covers drafting email replies that sound human, thread correctly, and render properly across email clients. It is scoped to response drafting — not marketing campaigns or mass outreach.
Draft-First: The Non-Negotiable Rule
Never send an email without the user's explicit approval. The workflow:
- Compose the draft (in markdown, in the agent's chat, or in a file)
- Present recipients, subject, and body to the user for review
- Save as draft to Outlook (or the user's email client) if available
- Wait for the user to say "send," "send now," "reply now," or equivalent
- Send only after explicit approval
If intent is ambiguous ("looks good" could mean "I approve the draft" or "I'll send it myself"), ask for one-line confirmation before sending.
Voice and Tone Matching
The cardinal rule: match the sender's register.
| Relationship | Tone | Example opener |
|---|---|---|
| Internal team / contractors | Short, direct, no filler | "Sent the updated file. Let me know if anything looks off." |
| Existing clients (high trust) | Warm but efficient | "Quick update — the document is ready for your review." |
| New contacts / cold replies | Professional, value-first | Lead with what is relevant to them, not your credentials |
| Formal threads | Match their formality | If they write "Dear Steven," reply with "Dear [Name]," not "Hey!" |
Calibration signals
Read the sender's email for cues:
- Length — if they wrote 2 sentences, don't reply with 5 paragraphs
- Greeting style — mirror their "Hi" / "Hello" / "Dear" / no greeting
- Closing — mirror their "Best" / "Thanks" / "Regards" / no closing
- Emoji/exclamation use — match their energy level, don't exceed it
What to avoid
- Over-explaining process — state the outcome, not the journey. "The agreement is ready" beats "I reviewed the agreement, made several updates to sections 3 and 7, cross-referenced with our template library, and..."
- Filler phrases — "I hope this email finds you well" is noise. Start with the point.
- Quoting others on your own product — never attribute your product description to someone else
- Singling out one insight from a rich conversation — if you had a long call, reference the breadth of the discussion, don't cherry-pick
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.
- 5d ago First seen · 167 lines · 84 tokens per session scan A 7c927698556b
email-drafting is a skill published in the GitHub repository UseJunior/email-agent-mcp (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 84 tokens to every session and 1,889 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…