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 adaptyteam/adapty-skills --skill adapty-mailgit clone --depth 1 https://github.com/adaptyteam/adapty-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/adaptyteam/adapty-skills/adapty-mail)<a href="https://agentmods.dev/skills/adaptyteam/adapty-skills/adapty-mail"><img src="https://agentmods.dev/badge/skills/adaptyteam/adapty-skills/adapty-mail/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/adaptyteam/adapty-skills/adapty-mail"><img src="https://agentmods.dev/badge/skills/adaptyteam/adapty-skills/adapty-mail.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.00128 | $0.02096 |
| Opus 5.5 | $0.00051 | $0.00838 |
| Sonnet 5.5 | $0.00026 | $0.00419 |
| Haiku 4.5 | $0.00013 | $0.00210 |
Grade A, and why
adapty-mail 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 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.
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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adapty Mail
Adapty Mail writes email sequences that turn trial and lapsed users into subscribers, sends them from the app's own domain and links them to a web checkout. You work in it through the Adapty Mail MCP server, signed in as the user. Its tools act for real: a saved flow emails real people.
The server sends its own instructions (the order of work, the trigger table, generation and localization rules). Follow them. This skill adds what they leave out: connecting the server, telling Mail apart from the rest of Adapty, what only the dashboard can do, the confirmation before anything that sends or cannot be undone, and the work after launch.
Mail or the rest of Adapty
Three nouns mean different things in each product. Decide which one the user means before any call.
| The request mentions | It is |
|---|---|
| Email, campaign, sequence, sending domain, DNS, unsubscribe, bounce, open or click rate, a "Never purchased" or "Billing issue" flow | Adapty Mail: this skill |
| Placement, paywall or onboarding screen, Flow Builder, in-app, the SDK | Core Adapty: flow-generator, audiences, growth-advisor or adapty-integration |
| Only "flow", "segment" or "profile" | Ask once: "the email flow in Adapty Mail, or the in-app flow in Adapty?" |
A Mail segment filters Mail profiles and is not a placement audience. A Mail profile exists only for a user with an email, so Mail shows fewer profiles than Adapty does.
Connect the server
- Look for it. The server is connected when you hold tools named
whoami,onboarding_statusandcampaign_generate(your client may prefix them, for examplemcp__adaptymail__whoami). Callwhoami. An email back means you are signed in. - Not there: open
references/connect.md, find the user's client and give them that one block. Signing in happens in their browser and ends on an Approve button in the Adapty Mail dashboard; you cannot click it. Most clients load a new server only in a new session, so say that the conversation continues there. - There, but calls fail with 401, "not authenticated" or no tools listed: the client added
the server without signing in. Give the client's sign-in step from
references/connect.md.
What ships with it
2 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.
- 3d ago First seen · 138 lines · 128 tokens per session scan A 694ad4c92e83
adapty-mail is a skill published in the GitHub repository adaptyteam/adapty-skills (6 stars, last pushed today), licensed MIT. It adds 128 tokens to every session and 2,096 once invoked, about $0.0005 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-24.
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…