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 jezweb/vite-flare-starter --skill draft-emailgit clone --depth 1 https://github.com/jezweb/vite-flare-starterWrote 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/jezweb/vite-flare-starter/draft-email)<a href="https://agentmods.dev/skills/jezweb/vite-flare-starter/draft-email"><img src="https://agentmods.dev/badge/skills/jezweb/vite-flare-starter/draft-email/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/jezweb/vite-flare-starter/draft-email"><img src="https://agentmods.dev/badge/skills/jezweb/vite-flare-starter/draft-email.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 43 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.00033 | $0.00535 |
| Opus 5.5 | $0.00013 | $0.00214 |
| Sonnet 5.5 | $0.00007 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
draft-email 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 1mo 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Draft Email
When to use
The user wants to send an email and needs help writing it. They may have a clear ask ("draft an email to my client about the delay") or a vague one ("help me email Bob").
Steps
-
Gather context — if any of these are unclear, use
ask_questions:- Recipient (name + relationship: client, colleague, friend, stranger)
- Purpose (informing, requesting, apologising, declining, follow-up)
- Tone (formal, friendly, urgent, gentle)
- Specific information to include
- Any constraints (length, must-mention items)
-
Recall context — call
recallfor any saved facts about the recipient (e.g. previous email threads, preferences) if relevant. -
Draft the email with this structure:
- Subject line — specific, action-oriented (not "Hi" or "Following up")
- Greeting — appropriate to the relationship
- Opening — one sentence stating purpose if direct, or a brief warm acknowledgement if relationship-based
- Body — ideally 2-4 short paragraphs. One idea per paragraph.
- Action/ask — clearly state what you need from them and by when (if applicable)
- Closing — appropriate sign-off
-
Show as a contact card if you're drafting to someone whose details should be confirmed: use
show_contact. -
Offer to refine — use
offer_choiceswith "Make it shorter", "More formal", "More casual", "Add a specific point", "Looks good".
Style guidelines
- Match the tone the user signals — don't override their preferences.
- For formal: avoid contractions, use full names with titles, careful subject line.
- For casual: contractions OK, first names, conversational.
- For Australian English: use Australian spelling (recognise, organise, colour) unless told otherwise.
- Keep emails short. Most should be under 200 words.
What not to do
- Don't write "I hope this email finds you well" or other empty opener filler.
- Don't apologise excessively — one acknowledgement is enough.
- Don't include made-up details (dates, prices, names) — use placeholders like [DATE] if information is missing.
- Don't write a wall of text — break it up.
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.
- 1mo ago First seen · 46 lines · 33 tokens per session scan A 13c2a753c2f2
draft-email is a skill published in the GitHub repository jezweb/vite-flare-starter (49 stars, last pushed 22d ago), licensed MIT. It adds 33 tokens to every session and 535 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…