paywall-upgrade-cro

paywall-upgrade-cro is a skill for Claude Code, Codex from rajitsaha/100xprism. It costs 92 tokens per session (1,162 once invoked), scanned A, original, MIT.

A guide for improving the screens and messages that ask users to start paying, upgrade, or unlock a feature inside an app.

In plain words
What is it for?
Use it to plan or improve freemium upgrades, trial-ending screens, usage-limit messages, feature upsells, and other in-app payment prompts.
Why use it?
It helps teams present an upgrade after users have seen the product’s value, without hiding the free option or making the decision feel forced.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to plan or improve freemium upgrades, trial-ending screens, usage-limit messages, feature upsells, and other in-app payment prompts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rajitsaha/100xprism/paywall-upgrade-cro
Install

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.

Any agent
npx skills add rajitsaha/100xprism --skill paywall-upgrade-cro
Clone the repo
git clone --depth 1 https://github.com/rajitsaha/100xprism

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for paywall-upgrade-cro

README.md
[![agentmods](https://agentmods.dev/badge/skills/rajitsaha/100xprism/paywall-upgrade-cro/github.svg)](https://agentmods.dev/skills/rajitsaha/100xprism/paywall-upgrade-cro)
Your own site
<a href="https://agentmods.dev/skills/rajitsaha/100xprism/paywall-upgrade-cro"><img src="https://agentmods.dev/badge/skills/rajitsaha/100xprism/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.

agentmods 80×15 button for paywall-upgrade-cro

Your own site · 80×15
<a href="https://agentmods.dev/skills/rajitsaha/100xprism/paywall-upgrade-cro"><img src="https://agentmods.dev/badge/skills/rajitsaha/100xprism/paywall-upgrade-cro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,162 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00092 $0.01162
Opus 5 $0.00046 $0.00581
Sonnet 5 $0.00018 $0.00232
Haiku 4.5 $0.00009 $0.00116

Measured 11d ago against content hash 336ae2ee66c9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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.

.agents/skills/paywall-upgrade-cro/SKILL.md · 152 lines

How it starts

The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Paywall and Upgrade Screen CRO

Convert free users to paid — or users to higher tiers — at moments when they've experienced enough value to justify the commitment.

Initial Assessment

Product context: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it first and tailor output to it; only ask for what it doesn't cover.

Understand first:

  1. Upgrade Context - Freemium → Paid? Trial → Paid? Tier upgrade? Feature upsell? Usage limit?
  2. Product Model - What's free? What's behind paywall? What triggers prompts? Current conversion rate?
  3. User Journey - When does this appear? What have they experienced? What are they trying to do?

Core Principles

  1. Value Before Ask — user has experienced real value first; upgrade feels like the natural next step. Timing: after "aha moment," not before.
  2. Show, Don't Just Tell — demonstrate paid-feature value, preview what they're missing, make the upgrade tangible.
  3. Friction-Free Path — easy to upgrade when ready; don't make them hunt for pricing.
  4. Respect the No — don't trap or pressure; easy to continue free; maintain trust for future conversion.

Paywall Trigger Points

  • Feature gates (user clicks a paid-only feature): explain why it's paid, show what the feature does, quick path to unlock, option to continue without.
  • Usage limits (user hits a limit): clear indication of limit reached, show what upgrading provides, don't block abruptly.
  • Trial expiration: early warnings (7, 3, 1 day), clear "what happens" on expiration, summarize value received.
  • Time-based prompts (after X days of free use): gentle reminder, highlight unused paid features, easy to dismiss.

Paywall Screen Components

  1. Headline - focus on what they get: "Unlock [Feature] to [Benefit]"
  2. Value Demonstration - preview, before/after, "With Pro you could..."
  3. Feature Comparison - highlight key differences, current plan marked
  4. Pricing - clear, simple, annual vs. monthly options
  5. Social Proof - customer quotes, "X teams use this"
  6. CTA - specific and value-oriented: "Start Getting [Benefit]"
  7. Escape Hatch - clear "Not now" or "Continue with Free"

Read the full file on GitHub · 152 lines

Files

What ships with it

3 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.

Changes

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.

  1. 11d ago First seen · 152 lines · 92 tokens per session scan A 336ae2ee66c9

Subscribe to this mod's changes

paywall-upgrade-cro is a skill published in the GitHub repository rajitsaha/100xprism (10 stars, last pushed 11d ago), licensed MIT. It adds 92 tokens to every session and 1,162 once invoked, about $0.0005 per session on Opus 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-08-31.