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 khadinakbarlabs/shopify-app-builder --skill app-pricing-strategygit clone --depth 1 https://github.com/khadinakbarlabs/shopify-app-builderWrote 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/khadinakbarlabs/shopify-app-builder/app-pricing-strategy)<a href="https://agentmods.dev/skills/khadinakbarlabs/shopify-app-builder/app-pricing-strategy"><img src="https://agentmods.dev/badge/skills/khadinakbarlabs/shopify-app-builder/app-pricing-strategy/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/khadinakbarlabs/shopify-app-builder/app-pricing-strategy"><img src="https://agentmods.dev/badge/skills/khadinakbarlabs/shopify-app-builder/app-pricing-strategy.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.00146 | $0.09909 |
| Opus 5 | $0.00073 | $0.04954 |
| Sonnet 5 | $0.00029 | $0.01982 |
| Haiku 4.5 | $0.00015 | $0.00991 |
Grade A, and why
app-pricing-strategy 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 10d 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 — 881 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shopify App Pricing Strategy
Frontmatter Triggers
- "How much should I charge for my app?"
- "What's the best pricing model for my Shopify app?"
- "Should I do free, freemium, or paid-only?"
- "How do I price a usage-based app?"
- "What's the right free trial length?"
- "How do competitors price similar apps?"
- "When and how should I raise my prices?"
- "How do I structure my pricing tiers?"
The Four Proven Pricing Models
1. Flat Tiered (Most Common)
When: 90% of successful Shopify apps use this. Pick it unless you have a reason not to.
How it works:
- 3–4 fixed price points (e.g., Starter $9.99, Growth $29.99, Scale $99.99)
- Each tier unlocks fixed feature sets + user/order limits
- Revenue is completely predictable
- Easy to communicate
Real Shopify examples:
- Klaviyo Email Marketing: Free, $20, $50, $150, $500/mo (tier by contact count)
- Gorgias Help Desk: Free, $50, $150, $400, $1000/mo (tier by conversation volume)
- Printful Print-on-Demand: Free + rev-share, then flat fees by service tier
Conversion lift by tier:
- Starter tier: 40–60% of free trial users convert
- Growth tier: 15–25% of Starter converts to Growth
- Scale tier: 5–10% of Growth converts to Scale
Shopify revenue share and fees:
- Eligible standard-rate developers keep 100% of the first $1M in lifetime gross app revenue earned since January 1, 2025.
- Above $1M, Shopify's revenue share is 15% and the developer keeps 85% before other fees and taxes.
- All billing also has a separate 2.9% processing fee, applicable sales tax, and possible regional fees.
- Revenue is aggregated across apps and associated developer accounts. Very large developers have separate eligibility rules.
Pro tip: Design tiers so the "sweet spot" (Growth/Scale tier) is your profit engine. Starter should feel limited but functional. Scale should feel unreachable to most but desirable.
2. Usage-Based (For Data/Computation/API Heavy)
When: Your cost to serve grows with merchant activity (emails sent, API calls, storage, image uploads)
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.
- 10d ago First seen · 881 lines · 146 tokens per session scan A 9fa73716c88b
app-pricing-strategy is a skill published in the GitHub repository khadinakbarlabs/shopify-app-builder (1 stars, last pushed 1mo ago), licensed MIT. It adds 146 tokens to every session and 9,909 once invoked, about $0.0007 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
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
ebay-search
Search eBay listings - find items, auctions, deals, and compare prices.
ulw-execute
Executes a written Prometheus work plan with Boulder state, evidence ledger, worktree discipline, and parallel subagents. Use when the user says ulw-execute or asks to run a .omo/plans plan.
frontend
Builds, styles, and polishes web UI and UX. Use for any frontend, page, component, styling, layout, animation, or visual-quality task, or when asked to make an interface look or feel a certain way.
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.
lcx-report-bug
Create a high-signal bug issue or PR in the repo that owns the defect. Use this whenever the user asks to report, file, open, or triage a LazyCodex, lazycodex-ai, omo-codex, Codex plugin, or upstream Codex CLI bug, especially when they need source-backed root cause, reproduction steps, fix guidance, and GitHub routing.