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 onboarding-teardowngit 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/onboarding-teardown)<a href="https://agentmods.dev/skills/adaptyteam/adapty-skills/onboarding-teardown"><img src="https://agentmods.dev/badge/skills/adaptyteam/adapty-skills/onboarding-teardown/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/onboarding-teardown"><img src="https://agentmods.dev/badge/skills/adaptyteam/adapty-skills/onboarding-teardown.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.00190 | $0.07392 |
| Opus 5.5 | $0.00076 | $0.02957 |
| Sonnet 5.5 | $0.00038 | $0.01478 |
| Haiku 4.5 | $0.00019 | $0.00739 |
Grade A, and why
onboarding-teardown 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 10d 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 — 483 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboarding Teardown
You are running the onboarding teardown that Adapty's team performs on top subscription apps. Someone describes their flow (or sends screens, a render, or the flow config); you give back a prioritized set of testable hypotheses, each grounded in a pattern seen across top apps, with an expected impact range.
The value is not generic advice ("add personalization"). It is the pattern + the specific application + the grounding + the number: "your loader promises a personalized plan and then hands users to the paywall — add the plan-summary payoff between them; near-universal in wellness, expect CR +10–20%." Never collapse to generic tips.
Treat onboarding and the paywall as one funnel. The strongest findings live at the seam: a goal
captured in onboarding that the paywall never mentions, a loader that promises personalization the
next screen doesn't deliver. A flow teardown that stops at the paywall's edge misses the most
valuable half. The paywall screen's own execution — plan cards, price display, CTA, proof
placement — belongs to paywall-teardown; see Scope.
How you sound
Every line the user reads, the fixed blocks included:
- A growth colleague who has seen many onboardings. Specific to this flow, honest when it is already good, never padded to look thorough.
- "I" for what you do, "you" for what they do. Lead with the read-back; end on one next step. No opener, no recap of what they sent, no narration of your process ("I read the config, so I won't ask…"), no "let me know if…".
- Bold at most one thing per paragraph. Section labels, table rows and the screen names in the read-back need no bold; quotes mark a screen name.
- Raw values only when the user will see them elsewhere — a screen name or button label from their builder, a price. Never element ids or tool names.
- Full, clickable links.
- Reply in the user's language — the disclaimer and the builder pitch too. Labels quoted from their flow stay exactly as the flow shows them.
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.
- 10d ago Changed · +5 lines a3f07bc7e4a9
- 14d ago Changed · +14 lines 22dfe9232614
- 19d ago Changed · +1 lines 88213b5863a7
- 20d ago Changed 96c649117fed
- 21d ago Changed · +47 lines 2deae51ff4bc
- 1mo ago Changed · +3 lines 9f981e35adb9
- 1mo ago First seen · 413 lines · 190 tokens per session scan A 2f0cf6af3075
onboarding-teardown is a skill published in the GitHub repository adaptyteam/adapty-skills (6 stars, last pushed today), licensed MIT. It adds 190 tokens to every session and 7,392 once invoked, about $0.0008 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-09-03.
Other skills, from other repositories
display-glasses-with-jetpack-compose-glimmer
Provides guidelines for developing projected Android XR apps for display glasses using the Jetpack Compose Glimmer UI toolkit. Covers Glimmer design principles, workflows, and interaction models for the glasses form factor. Use this skill to build an Android XR Augmented Experience app with Jetpack Compose Glimmer.…
glance-canonical-layouts
Use this skill to create home screen widgets using Jetpack Glance Canonical Layouts from the Android Platform Samples project, or when asked to implement standard widget layout patterns (including Check List, Image Grid, Snap Scrolling, and Standard Toolbar).
expo-design-system
Build and maintain a design system inside an Expo app - a reusable theme of design tokens (color, spacing, typography, radius, shadow, motion), reusable component structure with variant/size/state prop conventions, and rules for when to extract a repeated view into a shared component. Use when creating or organizing…
flutter-build-responsive-layout
Use LayoutBuilder, MediaQuery, or Expanded/Flexible to create a layout that adapts to different screen sizes. Use when you need the UI to look good on both mobile and tablet/desktop form factors.
omh-apple-design
This is an OMH apple-design workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
axiom-audit-liquid-glass
Use when the user mentions Liquid Glass review, iOS 26 UI updates, toolbar improvements, or visual effect migration.