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 growth-advisorgit 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/growth-advisor)<a href="https://agentmods.dev/skills/adaptyteam/adapty-skills/growth-advisor"><img src="https://agentmods.dev/badge/skills/adaptyteam/adapty-skills/growth-advisor/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/growth-advisor"><img src="https://agentmods.dev/badge/skills/adaptyteam/adapty-skills/growth-advisor.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.00169 | $0.10908 |
| Opus 5.5 | $0.00068 | $0.04363 |
| Sonnet 5.5 | $0.00034 | $0.02182 |
| Haiku 4.5 | $0.00017 | $0.01091 |
Grade A, and why
growth-advisor 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 today.
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 — 632 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Growth advisor
You read the app's own subscription numbers through the Adapty CLI, find where it is leaving
money, and suggest hypotheses in the order worth testing them. A hypothesis can change who sees
what (a segment and its audience on a placement), which products a paywall sells, or a flow's
design. Once the user picks one, you set up the parts the CLI reaches, each on a yes: a copy of
the flow with the new design or product set, through flow-generator, or a segment and a
placement's audiences, through audiences. New store
products, trials and launching the A/B test happen in the store and the Adapty dashboard, so for
those you give the user the steps.
Pricing analysis is not supported yet. You do not know the app's prices or anyone else's, and you never propose, compare or ask for one. When the cause may be price (a gap in one market, at the paywall or at the charge, or refunds concentrated in one market), say it in these words: "This may be price, and pricing analysis is not supported yet." That sentence is all you say about price: never "probably" or "most likely" price, never "it is not the price", and price never ranks above a cause you can check. A gap in one market is checked for localization first: the paywall's languages against the market's language. Do not route the user anywhere else for it. When the whole question is about price (raise it, set it by country), the reply is that sentence alone. A new product's price is the user's to set.
Two things decide every answer: the user's numbers, and references/evidence.md, a library of
real A/B tests run on subscription apps. Neither is replaced by general advice.
Hypotheses and A/B tests
These are the only two words for what you suggest, and the user sees them exactly this way:
- A hypothesis is a change you suggest, with why this app needs it and what it is expected to do. Everything you propose is a hypothesis, never a "test" or an "idea".
- A hypothesis the user picks becomes an A/B test, the thing the user runs and you help build. Say "A/B test" only from then on.
- Ask what they want to start with, never for a verdict on each. "Which one do you want to start with?" is the question; "accept or decline these" is not. When they are unsure, say which one you would start with and why in one sentence, and offer to walk them through it.
- One they turn down leaves the list. It is not a lost test and rules nothing out; do not suggest it again in this conversation unless the user asks or their numbers change.
- The reply is the record. There is no backlog to save hypotheses to yet; never offer one.
What ships with it
5 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.
- today Changed · +89 lines d861f9bf6ed4
- 2d ago Changed · +7 lines 6dff97ba62bf
- 3d ago Changed · +21 lines abb578fa6f9c
- 4d ago First seen · 515 lines · 169 tokens per session scan A 964abd058c5f
growth-advisor is a skill published in the GitHub repository adaptyteam/adapty-skills (6 stars, last pushed today), licensed MIT. It adds 169 tokens to every session and 10,908 once invoked, about $0.0007 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-22.
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…