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 winsenlabs/platos --skill email_sendgit clone --depth 1 https://github.com/winsenlabs/platosWrote 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/winsenlabs/platos/email_send)<a href="https://agentmods.dev/skills/winsenlabs/platos/email_send"><img src="https://agentmods.dev/badge/skills/winsenlabs/platos/email_send/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/winsenlabs/platos/email_send"><img src="https://agentmods.dev/badge/skills/winsenlabs/platos/email_send.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.00028 | $0.00894 |
| Opus 5 | $0.00014 | $0.00447 |
| Sonnet 5 | $0.00006 | $0.00179 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
Email Send 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.
What it actually says
You can send transactional emails through Resend.
When to use send_email:
- The user explicitly asks you to send an email (confirmation, notification, follow-up).
- An operator-configured workflow requires email delivery (alerts, digests, escalations).
Required arguments:
to— recipient email address (single string or array up to 50).subject— non-empty subject line.htmland/ortext— at least one body format. Preferhtmlfor rich formatting; includetextas a fallback when both audience reach and accessibility matter.
Optional arguments:
from— sender address. Must be on a domain you've verified in resend.com/domains. When omitted, falls back toRESEND_FROM_EMAIL. The skill fails if neither is set — Resend rejects unverified senders.replyTo— where replies go (defaults tofrom).cc/bcc— additional recipients.tags—[{name, value}]pairs for Resend's dashboard analytics (e.g.{name: "category", value: "billing"}).
Guidelines:
- Always confirm the recipient and subject with the user before sending unless an upstream workflow has authorised it.
- Prefer concise, well-formatted HTML (inline styles work; external CSS does not).
- Don't include the user's auth tokens, API keys, or other secrets in email bodies.
- For bulk sends to >5 recipients, prefer creating a Resend audience + broadcast in the dashboard rather than long
toarrays — this skill is for transactional, not marketing, traffic.
On error:
The tool returns { ok: false, error: "<reason>" } when Resend rejects the request. Common reasons: unverified from domain, malformed recipient, body missing, payload too large. Surface the reason to the user so they can correct it.
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 · 50 lines · 28 tokens per session scan A 91306e79a28f
Email Send is a skill published in the GitHub repository winsenlabs/platos (24 stars, last pushed today), licensed Apache-2.0. It adds 28 tokens to every session and 894 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-09-04.
Other skills, from other repositories
cn-check
Install and run the Continue CLI (cn) to execute AI agent checks on local code changes. Use when asked to "run checks", "lint with AI", "review my changes with cn", or set up Continue CI locally.
bio-ortholog-inference
Pull pre-computed ortholog calls from public databases (OrthoDB, Ensembl Compara, OMA browser, eggNOG, PANTHER, KEGG Orthology, HomoloGene) via their REST APIs. Use when orthologs are already curated upstream, when the question is "what is the X ortholog of Y" rather than "how to infer orthology de novo", when…
admet_genetic
ADMET-guided genetic molecule optimization workflow from seed SMILES; use when the agent needs to build or run an RDKit/SA-Score/ADMET-AI GA pipeline for molecule optimization, enforce molecule lineage logs, render optimization-history HTML dashboards, and write candidate triage reports.
bioprobench
Score an LLM's biological-protocol reasoning on the BioProBench benchmark: protocol QA, step ordering, error detection, protocol generation, and LLM-judged error reasoning; or generate the responses.
alphafold2
Predict protein structure for monomers and multimers with AlphaFold2 via the ColabFold runner (Mirdita et al. 2022, github.com/sokrypton/ColabFold; AlphaFold2 Jumper et al. 2021). Reach for this skill to fold a sequence or complex with the AF2/AF2-Multimer evoformer, to validate designed sequences by self-consistency…
audit-dataset
Audit tabular datasets before analysis or training for schema drift, missing values, duplicate rows or IDs, target imbalance, and entity or group leakage across splits using pure-stdlib helpers.