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-listing-optimizationgit 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-listing-optimization)<a href="https://agentmods.dev/skills/khadinakbarlabs/shopify-app-builder/app-listing-optimization"><img src="https://agentmods.dev/badge/skills/khadinakbarlabs/shopify-app-builder/app-listing-optimization/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-listing-optimization"><img src="https://agentmods.dev/badge/skills/khadinakbarlabs/shopify-app-builder/app-listing-optimization.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.00158 | $0.05971 |
| Opus 5 | $0.00079 | $0.02985 |
| Sonnet 5 | $0.00032 | $0.01194 |
| Haiku 4.5 | $0.00016 | $0.00597 |
Grade A, and why
app-listing-optimization 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 8d 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 — 566 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use This Skill
You're building a Shopify app and need to maximize discoverability and conversion from listing visit → install → trial activation → paid customer. This skill guides you through the mechanics of Shopify App Store ranking, listing copy psychology, visual assets, and pre-submission validation.
Use this when:
- You have an MVP ready for App Store submission
- Your app is live but getting <10 installs/week
- You want to optimize pricing presentation
- You need to understand what the Shopify algorithm actually rewards
- You're A/B testing your listing
The Shopify App Store Ranking Algorithm: What Actually Matters
Shopify's search ranking is opaque but pattern-driven. Your ranking is determined by these factors (approximate weights):
| Factor | Weight | What It Means | How to Optimize |
|---|---|---|---|
| Install Velocity | 35% | Installs per week in past 30 days | Pre-launch with waitlist, drive first-week traffic, ask beta customers to install day 1 |
| Uninstall Rate | 25% | % of installs that uninstall | Focus on retention, quick onboarding, bug fixes |
| Rating + Review Recency | 20% | 5-star ratings + freshness of reviews | Ask satisfied customers for reviews within 48h of install |
| Title Keyword Match | 10% | Does your title contain the searched keyword? | Use problem + benefit in title |
| Category Fit + Specificity | 10% | Is the app in the right category? | Choose most specific category available, don't try multiple |
Critical insight: Install velocity is 35% of the ranking algorithm. This means a 3-day launch sprint where you drive 50 installs beats slow organic growth. Your ranking in week 1 determines your visibility for months.
Conversion benchmarks (typical):
- App Store listing visit → install: 3-8% (varies by category, copy quality)
- Free install → trial activation: 40-65% (depends on onboarding clarity)
- Trial → paid conversion: 15-35% (depends on price fit + product quality)
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.
- 8d ago First seen · 566 lines · 158 tokens per session scan A 302be00cd106
app-listing-optimization is a skill published in the GitHub repository khadinakbarlabs/shopify-app-builder (1 stars, last pushed 29d ago), licensed MIT. It adds 158 tokens to every session and 5,971 once invoked, about $0.0008 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.