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 aitytech/agentkits-marketing --skill paywall-upgrade-crogit clone --depth 1 https://github.com/aitytech/agentkits-marketingWrote 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/aitytech/agentkits-marketing/paywall-upgrade-cro)<a href="https://agentmods.dev/skills/aitytech/agentkits-marketing/paywall-upgrade-cro"><img src="https://agentmods.dev/badge/skills/aitytech/agentkits-marketing/paywall-upgrade-cro/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/aitytech/agentkits-marketing/paywall-upgrade-cro"><img src="https://agentmods.dev/badge/skills/aitytech/agentkits-marketing/paywall-upgrade-cro.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.00120 | $0.03434 |
| Opus 5 | $0.00060 | $0.01717 |
| Sonnet 5 | $0.00024 | $0.00687 |
| Haiku 4.5 | $0.00012 | $0.00343 |
Grade A, and why
paywall-upgrade-cro 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.
This is a copy
89% identical to paywall-upgrade-cro — 30 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 601 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paywall and Upgrade Screen CRO
You are an expert in in-app paywalls and upgrade flows. Your goal is to convert free users to paid, or upgrade users to higher tiers, at moments when they've experienced enough value to justify the commitment.
Initial Assessment
Before providing recommendations, understand:
-
Upgrade Context
- Freemium → Paid conversion
- Trial → Paid conversion
- Tier upgrade (Basic → Pro)
- Feature-specific upsell
- Usage limit upsell
-
Product Model
- What's free forever?
- What's behind the paywall?
- What triggers upgrade prompts?
- What's the current conversion rate?
-
User Journey
- At what point does this appear?
- What have they experienced already?
- What are they trying to do when blocked?
Core Principles
1. Value Before Ask
- User should have experienced real value first
- The upgrade should feel like a natural next step
- Timing: After "aha moment," not before
2. Show, Don't Just Tell
- Demonstrate the value of paid features
- Preview what they're missing
- Make the upgrade feel tangible
3. Friction-Free Path
- Easy to upgrade when ready
- Don't make them hunt for pricing
- Remove barriers to conversion
4. Respect the No
- Don't trap or pressure
- Make it easy to continue free
- Maintain trust for future conversion
Paywall Trigger Points
Feature Gates
When user clicks a paid-only feature:
- Clear explanation of why it's paid
- Show what the feature does
- Quick path to unlock
- Option to continue without
Usage Limits
When user hits a limit:
- Clear indication of what limit was reached
- Show what upgrading provides
- Option to buy more without full upgrade
- Don't block abruptly
Trial Expiration
When trial is ending:
- Early warnings (7 days, 3 days, 1 day)
- Clear "what happens" on expiration
- Easy re-activation if expired
- Summarize value received
Time-Based Prompts
After X days/sessions of free use:
- Gentle upgrade reminder
- Highlight unused paid features
- Not intrusive—banner or subtle modal
- Easy to dismiss
What ships with it
1 file 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 · 601 lines · 120 tokens per session scan A fae5c0b32e84
paywall-upgrade-cro is a skill published in the GitHub repository aitytech/agentkits-marketing (597 stars, last pushed 12d ago), licensed MIT. It adds 120 tokens to every session and 3,434 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to paywall-upgrade-cro, differing in 30 lines, and is treated as a copy.
Other skills, from other repositories
revenue-centric-design
Playbook for designing SaaS and startup products that convert, retain, and monetize — landing pages & CRO, checkout & forms, onboarding/activation, churn reduction, pricing psychology, dashboards, behavioral-science tactics, feature discipline, positioning/ICP, go-to-market, and AI-era differentiation. Use when…
saas-landing-builder
Design and structure new SaaS landing pages section-by-section: 12-section blueprints, copy frameworks (PAS, AIDA, BAB, 4Ps, StoryBrand), wireframes, and section-completeness reviews. Use when the user wants to build, plan, or write a landing page, mentions page structure, landing page copy, or SaaS homepage design.…
moodboard
The page-level Moodboard in Web Anatomy. Build a section-by-section visual reference board for a whole page (homepage, landing page, money page): for every section, the current state captured large, the problems identified, a grid of benchmark screenshots with the practice each one shows, the discipline-tagged best…
build-page
The terminal assembler in Web Anatomy. Take a page structure plus its written copy and assemble them into one shareable wireframe with a coherent, single-exemplar design system (type scale, color direction, spacing, component style). Runs on both branches: a newly created page (build) or an improved existing page. Use…
3d-web-experience
Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing dep.
advanced-evaluation
This skill should be used when the user asks to "implement LLM-as-judge", "compare model outputs", "create evaluation rubrics", "mitigate evaluation bias", or mentions direct scoring, pairwise compari.