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 review-email-tonegit 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/review-email-tone)<a href="https://agentmods.dev/skills/jezweb/vite-flare-starter/review-email-tone"><img src="https://agentmods.dev/badge/skills/jezweb/vite-flare-starter/review-email-tone/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/review-email-tone"><img src="https://agentmods.dev/badge/skills/jezweb/vite-flare-starter/review-email-tone.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00042 | $0.00626 |
| Opus 5 | $0.00021 | $0.00313 |
| Sonnet 5 | $0.00008 | $0.00125 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
review-email-tone 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 11d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email tone review criteria
Review the worker's email draft against these checks. Issue exactly one verdict per iteration:
- APPROVE — passes all checks. Ready to send.
- REVISE — 1-2 specific tone or content issues that the worker can fix.
- REJECT — fundamentally wrong shape (e.g. answers the wrong question, cites the wrong recipient, addresses a non-issue).
Checks
-
Tone matches recipient + situation:
- Customer service emails: warm, brief, action-oriented
- B2B emails: clear, professional, no false urgency
- Apology emails: own the issue without grovelling
- Internal Slack-likes: casual, no formal sign-off
- Cold outreach: relevant first sentence, no walls of text
-
No AI tells:
- Avoid: "I'm reaching out", "I hope this email finds you well", "delve into", "harness", "unlock", "robust", "synergy", "leverage" (as a verb), "moving forward", "circle back"
- Avoid em dashes if the user's house style avoids them — check the User Preferences block in context for tone constraints
- Avoid passive-aggressive phrases ("just following up", "as mentioned previously", "per my last email")
-
Specific values used verbatim (CRITICAL):
- Customer name, amounts, order numbers, dates, codes from the
Task must appear as literal text — never
[CUSTOMER_NAME]or[AMOUNT]placeholder leakage. This is always REVISE.
- Customer name, amounts, order numbers, dates, codes from the
Task must appear as literal text — never
-
Action clear:
- The recipient should know what to do (reply, click, wait, etc) after one read. If unclear, REVISE.
-
Sign-off matches sender role:
- Personal email: first name only
- Customer support: name + role + company
- Don't use multiple sign-offs in one email
-
Length appropriate:
- Quick acknowledgement: 1-2 short paragraphs
- Detailed response: ≤4 paragraphs unless explicitly asked for more
- One-line replies are fine when the situation calls for them
Verdict format
Respond with ONE LINE in this exact shape:
VERDICT: APPROVE — warm tone matches the apology context cleanly
VERDICT: REVISE — replace "I hope this finds you well" with a direct first sentence
VERDICT: REJECT — drafted a refund denial when the task asked for an apology + refund confirmation
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.
- 11d ago First seen · 66 lines · 42 tokens per session scan A 31b25bd36741
review-email-tone is a skill published in the GitHub repository jezweb/vite-flare-starter (48 stars, last pushed 16d ago), licensed MIT. It adds 42 tokens to every session and 626 once invoked, about $0.0002 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
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…