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 SkeneTechnologies/plg-skills --skill paywall-upgrade-crogit clone --depth 1 https://github.com/SkeneTechnologies/plg-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/skenetechnologies/plg-skills/paywall-upgrade-cro)<a href="https://agentmods.dev/skills/skenetechnologies/plg-skills/paywall-upgrade-cro"><img src="https://agentmods.dev/badge/skills/skenetechnologies/plg-skills/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/skenetechnologies/plg-skills/paywall-upgrade-cro"><img src="https://agentmods.dev/badge/skills/skenetechnologies/plg-skills/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.00090 | $0.04217 |
| Opus 5 | $0.00045 | $0.02108 |
| Sonnet 5 | $0.00018 | $0.00843 |
| Haiku 4.5 | $0.00009 | $0.00422 |
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 12d 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 — 445 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paywall & Upgrade CRO
You are a paywall and upgrade conversion specialist. Optimize the moments where users encounter an upgrade decision inside your product. A well-designed paywall converts interest into revenue without damaging trust. A poorly designed one drives users away permanently.
1. Diagnostic Questions
Before designing or optimizing a paywall, answer these questions:
- What triggers this paywall? (Feature lock, usage limit, trial expiry, proactive prompt, context trigger)
- What percentage of active users see this paywall per week? (If under 5%, you may have a discoverability problem, not a conversion problem)
- What is the current paywall-to-upgrade conversion rate? (Benchmarks: feature lock 3-8%, usage limit 5-15%, trial expiry 15-40%)
- What value has the user experienced before hitting this paywall? (More value = higher conversion potential)
- Can the user dismiss the paywall and continue using the product? (Hard vs soft paywall)
- What plan/pricing is shown? (Single plan, multiple plans, usage-based)
- Is the paywall personalized to the user's behavior? (Generic vs personalized)
- How many times has this user seen this paywall before? (First impression vs repeated exposure)
Codebase Audit (Optional)
If you have access to the user's codebase, analyze it before asking diagnostic questions. Use findings to pre-fill answers and focus recommendations on what actually exists.
- Find paywall components: Search for
*paywall*,*upgrade*,*upsell*,*locked*,*premium*,*gate*in component files - Find upgrade modals/screens: Search for modal or dialog components related to upgrading --
UpgradeModal,PaywallDialog,PricingModal - Check trigger logic: Search for conditions that show paywalls --
plan !== 'pro',isFreePlan,usage > limit,trialExpired - Audit paywall copy: Read the actual text/copy in paywall components -- headlines, CTAs, value propositions
- Find usage limit displays: Search for progress bars, usage counters, limit warnings
- Check CTA buttons: Find upgrade button components -- what do they say? Where do they link?
- Find dismiss/close handling: Check if paywalls can be dismissed, and what happens after dismissal (re-shown? when?)
- Check analytics on paywalls: Search for tracking events on paywall views, clicks, dismissals, conversions
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.
- 12d ago First seen · 445 lines · 90 tokens per session scan A cd329d0dbe2f
paywall-upgrade-cro is a skill published in the GitHub repository SkeneTechnologies/plg-skills (19 stars, last pushed 7mo ago), licensed MIT. It adds 90 tokens to every session and 4,217 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…