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 rajitsaha/100xprism --skill paywall-upgrade-crogit clone --depth 1 https://github.com/rajitsaha/100xprismWrote 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/rajitsaha/100xprism/paywall-upgrade-cro)<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.
<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>- NVIDIA SkillSpector pass
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.00092 | $0.01162 |
| Opus 5.5 | $0.00037 | $0.00465 |
| Sonnet 5.5 | $0.00018 | $0.00232 |
| Haiku 4.5 | $0.00009 | $0.00116 |
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 1mo 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 — 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:
- Upgrade Context - Freemium → Paid? Trial → Paid? Tier upgrade? Feature upsell? Usage limit?
- Product Model - What's free? What's behind paywall? What triggers prompts? Current conversion rate?
- User Journey - When does this appear? What have they experienced? What are they trying to do?
Core Principles
- Value Before Ask — user has experienced real value first; upgrade feels like the natural next step. Timing: after "aha moment," not before.
- Show, Don't Just Tell — demonstrate paid-feature value, preview what they're missing, make the upgrade tangible.
- Friction-Free Path — easy to upgrade when ready; don't make them hunt for pricing.
- 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
- Headline - focus on what they get: "Unlock [Feature] to [Benefit]"
- Value Demonstration - preview, before/after, "With Pro you could..."
- Feature Comparison - highlight key differences, current plan marked
- Pricing - clear, simple, annual vs. monthly options
- Social Proof - customer quotes, "X teams use this"
- CTA - specific and value-oriented: "Start Getting [Benefit]"
- Escape Hatch - clear "Not now" or "Continue with Free"
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.
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.
- 1mo ago First seen · 152 lines · 92 tokens per session scan A 336ae2ee66c9
paywall-upgrade-cro is a skill published in the GitHub repository rajitsaha/100xprism (10 stars, last pushed today), licensed MIT. It adds 92 tokens to every session and 1,162 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
buywhere-product-catalog
Use BuyWhere's MCP and API surfaces to add product search, price comparison, and deal discovery to AI shopping agents.
billing-automation
Build automated billing systems for recurring payments, invoicing, subscription lifecycle, and dunning management. Use when implementing subscription billing, automating invoicing, or managing recu...
ordercli
Check past food delivery orders and track active order status via the ordercli CLI. Supports Foodora with history, reorder, and session management.
stripe-integration
Stripe payment integration. Checkout, subscriptions, webhooks, and billing management. Use when implementing payments or monetization in applications.
pricing-strategy
SaaS pricing models, freemium strategies, tier design, and competitive pricing. Use when designing pricing pages or monetization strategies.
apify-ecommerce
Extract product data, prices, reviews, and seller information from any e-commerce platform using Apify's E-commerce Scraping Tool.