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 RBraga01/builder-growth --skill pricing-page-reviewgit clone --depth 1 https://github.com/RBraga01/builder-growthWrote 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/rbraga01/builder-growth/pricing-page-review)<a href="https://agentmods.dev/skills/rbraga01/builder-growth/pricing-page-review"><img src="https://agentmods.dev/badge/skills/rbraga01/builder-growth/pricing-page-review/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/rbraga01/builder-growth/pricing-page-review"><img src="https://agentmods.dev/badge/skills/rbraga01/builder-growth/pricing-page-review.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.00065 | $0.01939 |
| Opus 5 | $0.00032 | $0.00970 |
| Sonnet 5 | $0.00013 | $0.00388 |
| Haiku 4.5 | $0.00006 | $0.00194 |
Grade A, and why
pricing-page-review 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.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pricing Page Review
The Law
A PRICING PAGE THAT CONFUSES IS A PRICING PAGE THAT LOSES THE SALE SILENTLY.
"The pricing speaks for itself" assumes the reader will do the work of comparing tiers, finding which one fits them, and trusting the numbers — work most readers abandon rather than complete.
Clarity + differentiation + per-tier fit + clear CTA + risk reversal + objection handling + comparison logic + honest anchoring + disclosed limitations + upgrade path + trust IS a reviewed pricing page.
When to Use
Trigger before:
- Publishing a new pricing or packaging page
- Changing prices, tiers, or what's included in any existing plan
- Launching a new plan, add-on, or usage-based pricing component
- Any time customer feedback or sales objections suggest the pricing page is the friction point in the funnel (confirmed via
funnel-analysis)
When NOT to Use
- Custom/enterprise pricing communicated only through sales conversations with no public page (review the sales deck and proposal templates instead, using the same principles)
- Internal cost or margin documents (a different audience and purpose than a customer-facing pricing page)
The Eleven Review Areas
A complete review covers all eleven. A pricing page can fail on just one of these and lose conversions that no amount of strength on the other ten will recover.
1 — Pricing Clarity
Can a reader state the price they would pay, in 10 seconds, without doing math or guessing what's excluded? Hidden fees, vague usage units, or pricing that requires a calculator to understand fails this.
2 — Plan Differentiation
Is it immediately clear what's different between tiers — not just "more of everything" but specific capabilities that map to specific customer needs? Tiers differentiated only by quantity (more seats, more credits) with no qualitative difference confuse readers about which tier they actually need.
3 — Target Customer Per Tier
Does each tier name (implicitly or explicitly) who it's for? "Starter / Pro / Enterprise" with no description of who fits each forces the reader to self-select with no guidance — most will pick the cheapest, unsure if they're underbuying.
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 · 158 lines · 65 tokens per session scan A 4b281c567146
pricing-page-review is a skill published in the GitHub repository RBraga01/builder-growth (2 stars, last pushed 2mo ago), licensed MIT. It adds 65 tokens to every session and 1,939 once invoked, about $0.0003 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.
Other skills, from other repositories
gr-blog-post
A Jekyll blog publishing workflow. Jekyll is a tool that turns text and templates into a website, and this workflow also prepares matching English, Japanese, and Korean posts.
gr-geo-cite
A guide for checking whether AI assistants such as ChatGPT, Claude, Perplexity, and Gemini mention or cite your website when answering set questions.
gr-seo-patrol
An automated SEO and GEO checking routine. SEO helps pages appear in search engines; GEO checks how they may be found and understood by AI-based search tools.
gingiris-reddit-marketing
🇺🇸 Reddit Marketing & Growth Playbook 2026 — The complete Reddit operations SOP for AI/SaaS founders. Covers account warming (Karma 0→500 in 20 days), shadow ban prevention, multi-account matrix via fingerprint browsers, subreddit selection across 10K+ communities, content templates (90/10 rule), Product Hunt ×…
gingiris-github-star-growth
A guide to steadily increasing the number of people who bookmark an open-source project on GitHub by building content, community, events, contributors, and ambassadors.
gingiris-growth-finder
Diagnose a product's growth model, stage, and current constraint, then route the request to the narrowest Gingiris specialist and execute it when installed. Use for broad or uncertain growth questions involving go-to-market, Product Hunt, GitHub stars, open-source marketing, B2B SaaS, PLG, ASO, SEO/GEO, AI citations…