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-billinggit 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-billing)<a href="https://agentmods.dev/skills/khadinakbarlabs/shopify-app-builder/app-billing"><img src="https://agentmods.dev/badge/skills/khadinakbarlabs/shopify-app-builder/app-billing/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-billing"><img src="https://agentmods.dev/badge/skills/khadinakbarlabs/shopify-app-builder/app-billing.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.00049 | $0.05514 |
| Opus 5 | $0.00024 | $0.02757 |
| Sonnet 5 | $0.00010 | $0.01103 |
| Haiku 4.5 | $0.00005 | $0.00551 |
Grade A, and why
app-billing 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 9d 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 — 896 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shopify App Billing
Shopify apps can charge merchants through Shopify's billing system. Charges are collected via the merchant's Shopify payment method and appear on their bill. Three models are supported: recurring (fixed monthly/annual), usage-based (pay-per-action), and one-time (one-off charges). You can also combine them (hybrid).
Revenue Share Model
For developers eligible for Shopify's standard rates:
- You keep 100% of the first $1,000,000 USD in lifetime gross app revenue earned from January 1, 2025.
- Above that threshold, Shopify's revenue share is 15%, so you keep 85% before other fees and taxes.
- All billing is separately subject to a 2.9% processing fee, applicable sales tax, and potentially regional regulatory fees.
- Shopify applies special eligibility rules to very large developers and aggregates revenue across associated developer accounts. Verify the current policy before financial modeling.
This means your pricing directly affects what you keep:
App charges $10 while eligible for the 0% revenue-share tier
├─ Merchant pays: $10.00
├─ Processing fee: $0.29, before tax or regional fees
└─ Developer amount before tax/regional fees: $9.71
App charges $100 above the $1M lifetime threshold
├─ Merchant pays: $100.00
├─ Revenue share: $15.00
├─ Processing fee: $2.90, before tax or regional fees
└─ Developer amount before tax/regional fees: $82.10
Planning rule: Model revenue share, processing fees, taxes, refunds, and cost to serve separately; don't assume gross charges equal payout.
Billing Models
1. Recurring (Fixed Interval)
Use Case: Subscription model (e.g., "Pro plan $99/month") Charging: First charge immediate on approval; subsequent charges on anniversary date Cancellation: Merchant can cancel anytime; charged through current period end
appSubscriptionCreate Mutation:
mutation CreateRecurringSubscription {
appSubscriptionCreate(
input: {
trialDays: 7
lineItems: [
{
plan: {
appRecurringPricingDetails: {
interval: MONTHLY # or ANNUAL
price: { amount: "9.99", currencyCode: "USD" }
}
}
}
]
returnUrl: "https://your-app.com/billing/confirm"
}
) {
appSubscription {
id
confirmationUrl # Merchant must visit this URL to approve
lineItems {
id
plan {
pricingDetails {
... on AppRecurringPricingDetails {
interval
price { amount currencyCode }
}
}
}
}
status # PENDING, ACTIVE, DECLINED, EXPIRED, FROZEN, CANCELLED
currentPeriodEnd
trialDays
trialEndsOn
}
userErrors {
field
message
}
}
}
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.
- 9d ago First seen · 896 lines · 49 tokens per session scan A 081716e59bd7
app-billing is a skill published in the GitHub repository khadinakbarlabs/shopify-app-builder (1 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 5,514 once invoked, about $0.0002 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.