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 mindbox-cloud/agent-skills --skill emailgit clone --depth 1 https://github.com/mindbox-cloud/agent-skillsWrote 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/mindbox-cloud/agent-skills/email)<a href="https://agentmods.dev/skills/mindbox-cloud/agent-skills/email"><img src="https://agentmods.dev/badge/skills/mindbox-cloud/agent-skills/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/mindbox-cloud/agent-skills/email"><img src="https://agentmods.dev/badge/skills/mindbox-cloud/agent-skills/email.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.00068 | $0.15487 |
| Opus 5.5 | $0.00027 | $0.06195 |
| Sonnet 5.5 | $0.00014 | $0.03097 |
| Haiku 4.5 | $0.00007 | $0.01549 |
Grade A, and why
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 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 — 574 lines — stays where its author put it; the contents beside it link to each section on GitHub.
email — email generation
Generates the technical layout of an email from a text description. The internal output for Ops is valid JSX, which is then converted into Mindbox editor JSON.
Skill boundaries
This is a portable JSX generator. It does not work directly with gallery/upload tools, mailing ID and rowVersion, or saving to Mindbox. All operational actions — uploading and finding images via Ops, JSX → JSON conversion, HTML rendering, PNG preview, reading campaign metadata/visual template, and saving — are performed by the companion skill email-ops. Generator uses JSON/HTML/PNG feedback from Ops to self-correct the JSX, but does not fix operational errors on its own and does not invent URLs. A request to change the template type ("rebuild it in the visual editor", "convert it to HTML") is not generation either: Ops leads the route, and the JSX is assembled after Ops decides where to save.
Communicating with the user
JSX, internal IDs and rowVersion are internal details of the Generator–Ops interaction.
In normal conversation with the user say "email", "email layout", "email content",
"preview" and "saving", not JSX, mailingInternalId, variantInternalId,
formatInternalId, rowVersion or visualTemplateRowVersion. Do not replace the terms Active/Draft:
if they are needed to pick a version precisely, use exactly Active/Draft.
Do not show raw JSX or GUIDs unless the user explicitly asked for code, export,
markup or technical details. Return backend errors verbatim, even if they
contain technical terms, tag names, line numbers or identifiers.
Feedback to developers
Pass feedback about the skill's work to the companion operational skill for Mindbox email —
the one whose description covers preview, save, gallery and Mindbox MCP calls
(email-ops in this package). It is the one that calls the MCP tools of the current
Mindbox/email MCP server. If you see a critical problem in the Generator rules
or the user asks to pass feedback to the developers, hand it to Ops and follow
its protocol: first show the full feedback text to the user, then get
explicit confirmation, and only then send it.
What ships with it
7 files 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.
- 11d ago First seen · 574 lines · 68 tokens per session scan A 50e54a1413a5
email is a skill published in the GitHub repository mindbox-cloud/agent-skills (6 stars, last pushed 9d ago), licensed MIT. It adds 68 tokens to every session and 15,487 once invoked, about $0.0003 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-10-03.
Other skills, from other repositories
prove-the-gates
Audit the repository's own checks — for each test, gate and CI script, establish what it guards, whether anything still runs it, and whether it actually fails when you break what it protects. Use when the user says "prove the gates", "are our tests real", "audit the test suite", "which checks are fake", "תוכיח את…
implementation-notes
Maintain an IMPLEMENTATIONNOTES.md decision log during any multi-step implementation session. Use this in EVERY session that involves writing or modifying code across more than one file, or any session expected to run longer than a few tool calls. Records decisions, deviations from plan, and open questions so nothing…
full-audit
Audit a whole repository in one pass — dispatch every applicable audit lane in parallel, prove the repo's own gates fail when they should, and return one evidence-backed report ranked by severity. Use when the user says "full audit", "audit this repo", "check the whole codebase", "תעשה אודיט מלא", "אודיט לריפו"…
fable-method
The routing logic of the Fable Method - decides which unknowns-discovery technique (blindspot-pass, interview-me, prototype-first, implementation-notes, merge-quiz) applies to the current task, and which to skip. Consult this at the START of any non-trivial task, or when the user says "fable", "the method", "how…
blindspot-pass
Run a blindspot scan to surface the user's unknown unknowns BEFORE implementing a task. Use this whenever the user starts a non-trivial task in a domain they say (or appear) to be unfamiliar with, whenever they say "blindspot", "unknowns", "what am I missing", "before we start", or when a request is vague enough that…
convergence-guard
Stop-loss discipline for implementation sessions - detect fix-loops and runaway token burn, and stop to replan instead of patching. Consult during any debugging or implementation session, especially when tests keep failing, the same file keeps being edited, or the user mentions stoploss, token budget, fix loops, or…