Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/khadinakbarlabs/shopify-app-buildernpx agentmods add skills/khadinakbarlabs/shopify-app-builder/merchant-pain-preventionWrote 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/merchant-pain-prevention)<a href="https://agentmods.dev/skills/khadinakbarlabs/shopify-app-builder/merchant-pain-prevention"><img src="https://agentmods.dev/badge/skills/khadinakbarlabs/shopify-app-builder/merchant-pain-prevention/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/merchant-pain-prevention"><img src="https://agentmods.dev/badge/skills/khadinakbarlabs/shopify-app-builder/merchant-pain-prevention.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.00162 | $0.10825 |
| Opus 5 | $0.00081 | $0.05412 |
| Sonnet 5 | $0.00032 | $0.02165 |
| Haiku 4.5 | $0.00016 | $0.01082 |
Grade A, and why
merchant-pain-prevention 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 12d 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 — 685 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merchant Pain Prevention
Every 1-star review on the Shopify App Store is a merchant who trusted you and felt betrayed. This skill is the inverse of that experience — a hard-coded inventory of the patterns that cause the betrayal, with the structural fixes.
The merchant pain ecosystem is small and loud. Stores talk. Subreddits index. Community threads outrank the App Store on Google for the phrase "billed for uninstalled app" — there are at least eight active threads on that exact phrase. If you ship a billable app and get one of those patterns wrong, you will not just lose that merchant; you will repel the next 50 who Google your name.
This is not a style guide. It is a survival document. Follow it.
1. When to use
Invoke this skill whenever you are:
- Designing a new Shopify app or extension — before architecture is locked, before scopes are declared, before billing is wired.
- Reviewing a PR that touches: theme app extensions, ScriptTag, billing API, webhook handlers, scopes (
shopify.app.toml), onboarding flow, cancellation flow, email triggers, popups, banners, countdown timers, "social proof" widgets. - Pre-ship audit — the 48 hours before you submit to the App Store or release a new version.
- Triaging a merchant complaint — public 1-star, support ticket, refund request, chargeback, BBB complaint, Trustpilot drop, Reddit post that mentions your app by name.
- Annual reaudit — quarterly is better. Scopes accrete. Pricing pages drift. Anti-patterns sneak back in when feature flags collide.
- Investigating churn — a sudden uninstall spike usually maps to one of the cardinal pains.
If anyone on your team says "merchants will figure it out" or "this is industry standard" or "everyone does it this way" — that is the trigger to run this skill in full. Industry standard on Shopify is what generates 12 BBB complaints a day. Do not aim for industry standard.
2. The 7 cardinal merchant pains (ranked by anger)
Ranked by how fast they get you a public 1-star review, a chargeback, a Reddit post, and an unrecoverable partner-reputation hit. Each is documented with verbatim merchant quotes.
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.
- 12d ago First seen · 685 lines · 162 tokens per session scan A 50c268b13ee1
merchant-pain-prevention is a skill published in the GitHub repository khadinakbarlabs/shopify-app-builder (1 stars, last pushed 1mo ago), licensed MIT. It adds 162 tokens to every session and 10,825 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
ebay-search
Search eBay listings - find items, auctions, deals, and compare prices.
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.
ulw-execute
Executes a written ulw-plan 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.
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.
ulw-loop
A goal-like loop that decomposes work into systematic, evidence-bound ultrawork steps. Use when the user wants a goal loop or durable, checkpointed execution.