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 bromso/metapowers --skill paywall-upgrade-crogit clone --depth 1 https://github.com/bromso/metapowersWrote 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/bromso/metapowers/paywall-upgrade-cro)<a href="https://agentmods.dev/skills/bromso/metapowers/paywall-upgrade-cro"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/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/bromso/metapowers/paywall-upgrade-cro"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/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.00077 | $0.00733 |
| Opus 5.5 | $0.00031 | $0.00293 |
| Sonnet 5.5 | $0.00015 | $0.00147 |
| Haiku 4.5 | $0.00008 | $0.00073 |
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 3d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paywall & Upgrade CRO
Optimize the paywall and upgrade experience for "$ARGUMENTS". Design upgrade triggers, pricing page optimization, and conversion flows.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .metapowers/marketing/<project>/skip-log.md: - <ISO timestamp> — <skill name> skipped prerequisite check for <artifact file> — reason: <reason or "none given">.
Prerequisites
Read .metapowers/marketing/<project>/00-strategy.md. If this file does not exist, tell the user:
Phase 0 (Strategy) has not been completed for "". Run
/marketing:customer-research <project>first, or use--skip-checksto bypass.
Process
-
Read context:
- Read
.metapowers/marketing/<project>/00-strategy.mdfor pricing strategy - Read
.metapowers/marketing/<project>/04-engage.mdif it exists
- Read
-
Analyze current paywall (if applicable):
- When and where does the user hit the paywall?
- What's the messaging at the paywall moment?
- Hard paywall vs. soft paywall vs. metered approach
- How does it make the user feel? (frustrated vs. motivated)
-
Optimize upgrade triggers:
- Usage-based triggers: hitting limits naturally during valuable workflows
- Feature-based triggers: showing premium features with upgrade prompt
- Timing-based triggers: trial ending, usage milestone
- Social triggers: team features, collaboration needs
-
Pricing page optimization:
- Tier presentation: recommended tier highlighting
- Feature comparison clarity
- Social proof on pricing page
- FAQ and objection handling
- Annual vs. monthly toggle design
-
Write the artifact — append to
.metapowers/marketing/<project>/04-engage.mdunder a## Paywall & Upgrade CROsection. Create the file with a# Engage — <project>heading if it does not exist; if a## Paywall & Upgrade CROsection already exists, replace only that section. The section contains:- Current Paywall Assessment — strengths and friction
- Upgrade Trigger Design — when and where to prompt
- Pricing Page Recommendations — layout, copy, social proof
- A/B Test Ideas — highest-impact tests
- Expected Impact — estimated conversion lift
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.
- 3d ago First seen · 57 lines · 77 tokens per session scan A 6b0b98f2029e
paywall-upgrade-cro is a skill published in the GitHub repository bromso/metapowers (2 stars, last pushed 3d ago), licensed MIT. It adds 77 tokens to every session and 733 once invoked, about $0.0003 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-21.
Other skills, from other repositories
design-method
Use when starting any design task — resolves register, sets the 3 dials, locks Gate 0, and routes to the right move and target skill.
design-webapp
Use when building or extending a dashboard, SaaS screen, or any authenticated app surface — use design-web instead for a marketing site.
react-tanstack-router
Use when implementing routing in a React app (NOT Next.js) with TanStack Router — file-based routes, loaders, search params.
fusecore
Use when creating modules, understanding FuseCore structure, or implementing features in a FuseCore modular-monolith Laravel project.
laravel-billing
Use when implementing subscriptions, invoices, payment methods, webhooks, or billing portals with Laravel Cashier (Stripe or Paddle).
laravel-permission
Use when implementing RBAC, role-based access control, or user authorization with Spatie Laravel Permission.