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 built-for-shopify-standardsgit 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/built-for-shopify-standards)<a href="https://agentmods.dev/skills/khadinakbarlabs/shopify-app-builder/built-for-shopify-standards"><img src="https://agentmods.dev/badge/skills/khadinakbarlabs/shopify-app-builder/built-for-shopify-standards/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/built-for-shopify-standards"><img src="https://agentmods.dev/badge/skills/khadinakbarlabs/shopify-app-builder/built-for-shopify-standards.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.00047 | $0.10057 |
| Opus 5 | $0.00023 | $0.05028 |
| Sonnet 5 | $0.00009 | $0.02011 |
| Haiku 4.5 | $0.00005 | $0.01006 |
Grade A, and why
built-for-shopify-standards 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 — 827 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Built for Shopify Standards
The official quality bar for Shopify App Store apps. Qualifying apps receive the Built for Shopify highlight and badge, additional App Store promotion, eligibility for promotion on other merchant surfaces, and priority review for future app submissions. BFS does not create a separate revenue-share tier.
This skill is the full requirement matrix as of May 2026, with rejection patterns, a 50-item self-check, and a decision tree to tell you whether you're ready to apply.
1. When to use this skill
Trigger this skill when:
- You're planning to submit an app for the Built for Shopify (BFS) designation
- You got a "fails to meet Built for Shopify standards" rejection and want to fix it
- You're scoping a v1 app and want to build to BFS from the start (cheaper than retrofitting)
- A merchant or partner mentioned your app "isn't Built for Shopify yet"
- You're doing a 90-day audit before reapplying after a previous BFS failure
- You're deciding whether the promotional benefits justify the implementation and ongoing-compliance work
- You want to know exactly what "integration depth" means in BFS-speak (it's specific)
- You're comparing your app against a competitor that has the badge and want to close the gap
- You're hitting LCP, INP, CLS, or API p95 problems and want to know the actual gate numbers
- You're wiring up GDPR webhooks and want to confirm BFS still requires all three
Don't use this skill for:
- General App Store submission (different bar — that's
app-validation) - Performance debugging itself (that's
app-performance— this skill references those thresholds but doesn't reteach them) - Polaris implementation details (that's a separate UI/design skill)
- Listing copy or screenshots (that's
app-listing-optimization) - Pricing strategy (that's
app-pricing-strategy)
This skill is the audit framework. The fix-it skills live elsewhere.
2. What Built for Shopify actually is
2.1 It's a designation, not a category
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 · 827 lines · 47 tokens per session scan A 46f734565365
built-for-shopify-standards is a skill published in the GitHub repository khadinakbarlabs/shopify-app-builder (1 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 10,057 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.