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/maludb-ed/htmx-php-builder/malumail-sendnpx skills add maludb-ed/htmx-php-builder --skill malumail-sendgit clone --depth 1 https://github.com/maludb-ed/htmx-php-builderWrote 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/maludb-ed/htmx-php-builder/malumail-send)<a href="https://agentmods.dev/skills/maludb-ed/htmx-php-builder/malumail-send"><img src="https://agentmods.dev/badge/skills/maludb-ed/htmx-php-builder/malumail-send.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.00146 | $0.02404 |
| Opus 5 | $0.00073 | $0.01202 |
| Sonnet 5 | $0.00029 | $0.00481 |
| Haiku 4.5 | $0.00015 | $0.00240 |
Grade B, and why
malumail-send scanned grade B with 2 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 3d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
r = requests.post("https://api.malumail.com/v1/send", Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS -X POST https://api.malumail.com/v1/send \ How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MaluMail Send API
Send transactional email over a small REST API. This is the live contract at
api.malumail.com — every field, status code, and behavior below matches the
running service. Do not invent fields or endpoints beyond what is listed here.
- Base URL:
https://api.malumail.com(HTTPS only; non-HTTPS →400) - Auth:
Authorization: Bearer <api-key>on every request - Bodies/responses: JSON
Prerequisites (one-time, in the portal at https://malumail.com/portal/)
- Verified sending domain. You may only send
froman address whose domain is verified on the account (ownership TXT +SPF include:_spf.malumail.com+ DKIM published). Unverifiedfromdomain →403. DKIM/SPF are then applied automatically; you never sign anything. - API key. Portal → API Keys → create. Shown once, unrecoverable.
Format
mm_+ 48 lowercase hex chars (regex^mm_[a-f0-9]{48}$). Store as a secret; never commit it. Revoking in the portal makes it401immediately.
Send an email — POST /v1/send
Request JSON:
| Field | Type | Required | Notes |
|---|---|---|---|
from |
string | yes | Valid email; its domain must be a verified sending domain (else 403). |
from_name |
string | no | Display name → "Name" <from>. |
to |
string | string[] | yes | 1–50 addresses. All go in one shared message (recipients see each other). |
subject |
string | yes | Non-empty. |
text |
string | one of | Plain-text body. |
html |
string | one of | HTML body. |
At least one of text/html is required. Both → multipart/alternative.
Server auto-generates Date, Message-ID, MIME-Version.
Success 200:
{"status":"sent","accepted":["[email protected]"],
"rejected":[{"email":"[email protected]","reason":"suppressed:bounce"},
{"email":"bad","reason":"invalid_address"}]}
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.
- 3d ago First seen · 207 lines · 146 tokens per session scan B 3764d07a506d
malumail-send is a skill published in the GitHub repository maludb-ed/htmx-php-builder (8 stars, last pushed 28d ago), licensed MIT. It adds 146 tokens to every session and 2,404 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…