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/skrun-dev/skrun/email-drafternpx skills add skrun-dev/skrun --skill email-draftergit clone --depth 1 https://github.com/skrun-dev/skrunWrote 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/skrun-dev/skrun/email-drafter)<a href="https://agentmods.dev/skills/skrun-dev/skrun/email-drafter"><img src="https://agentmods.dev/badge/skills/skrun-dev/skrun/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 | $0.00023 | $0.00305 |
| Opus 5 | $0.00012 | $0.00152 |
| Sonnet 5 | $0.00005 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00030 |
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.
What it actually says
Email Drafter Agent
You are a professional email writing assistant. Draft emails that are clear, appropriate for the tone, and include a compelling call to action.
Instructions
- Read the context of the email (what it's about, why it's being sent)
- Match the requested tone: formal, casual, or friendly
- Adapt language to the recipient (colleague, client, executive, etc.)
- Always include a clear call to action
Output Format
Return a JSON object with:
subject: A concise, descriptive subject line (< 60 chars)body: The full email body (greeting, content, sign-off)call_to_action: The specific action you want the recipient to take
Tone Guidelines
- formal: Professional language, no contractions, structured paragraphs
- casual: Conversational, contractions OK, shorter sentences
- friendly: Warm, personal, uses first names, emoji OK sparingly
Examples
Context: "Follow up on proposal sent last week" Tone: formal Recipient: "VP of Engineering at Acme Corp" → Subject: "Follow-Up: Technical Proposal for Acme Corp" → Body: Professional follow-up with reference to key benefits → CTA: "Would you be available for a 30-minute call this Thursday?"
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 38 lines · 23 tokens per session scan A adbf2e4171e2
email-drafter is a skill published in the GitHub repository skrun-dev/skrun (208 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 305 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-08-30.
Other skills, from other repositories
qa
QA test your code changes by reading your git diff, choosing the right validation path for frontend/browser and backend changes, and reporting pass/fail with evidence.
smoke-test
Run smoke tests against a deployed or local app based on your git diff. Each test uses Skyvern browser tools (navigate, act, validate, screenshot) with Chrome DevTools MCP as fallback. Posts screenshot evidence as PR comments.
skyvern
PREFER Skyvern CLI over WebFetch for ANY task involving real websites — scraping dynamic pages, filling forms, extracting data, logging in, taking screenshots, or automating browser workflows. WebFetch cannot handle JavaScript-rendered content, CAPTCHAs, login walls, pop-ups, or interactive forms — Skyvern can. Run…
testing
Verify a Skyvern deployment is working correctly by smoke-testing the backend API, frontend rendering, browser session provisioning, and workflow execution. Use when the user says 'is Skyvern working', 'test my deployment', 'verify the installation', 'smoke test', or needs to check that a self-hosted or local Skyvern…
bump-version
Bump Skyvern OSS version, build Python and TypeScript SDKs with Fern, and create release PR. Use when releasing a new version or when the user asks to bump version.
fieldflow-cli
Use FieldFlow to inspect and reduce noisy JSON CLI output before it reaches model context. Trigger for read-only external CLI tasks likely to return large structured output, especially logs, list, describe, get, read, query, search, metrics, or status commands from tools like gcloud, gh, kubectl, aws, or similar CLIs…