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 using-shopify-app-buildergit 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/using-shopify-app-builder)<a href="https://agentmods.dev/skills/khadinakbarlabs/shopify-app-builder/using-shopify-app-builder"><img src="https://agentmods.dev/badge/skills/khadinakbarlabs/shopify-app-builder/using-shopify-app-builder/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/using-shopify-app-builder"><img src="https://agentmods.dev/badge/skills/khadinakbarlabs/shopify-app-builder/using-shopify-app-builder.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.00100 | $0.00975 |
| Opus 5 | $0.00050 | $0.00487 |
| Sonnet 5 | $0.00020 | $0.00195 |
| Haiku 4.5 | $0.00010 | $0.00097 |
Grade A, and why
using-shopify-app-builder 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Shopify App Builder
Treat this skill as the router for the toolkit. Select focused skills before proposing code or operational changes.
Routing workflow
- Inspect the repository, framework, Shopify configuration, and the user's stated outcome.
- Classify the request with the routing table below.
- Read the selected skill files completely. Use the smallest set that covers the request.
- Verify time-sensitive platform behavior against current official Shopify documentation.
- Implement only what the user authorized, then run proportionate checks on the real affected surface.
Skill routing table
| Request | Start with | Add when needed |
|---|---|---|
| New app, scaffold, extension, or deployment plan | shopify-cli |
app-validation, app-niche-finder, app-auth, app-billing |
| Admin data or GraphQL error | admin-graphql |
metafields-metaobjects, webhooks, dev-troubleshooting |
| Legacy REST migration | admin-rest |
admin-graphql, migrate-rest-to-graphql command in Claude/Cursor |
| OAuth, token exchange, HMAC, or session issue | app-auth |
dev-troubleshooting, webhooks |
| Billing, plans, trials, or usage charges | app-billing |
app-pricing-strategy, merchant-pain-prevention |
| Embedded admin UI | app-bridge and polaris-ui |
ux-polaris-antipatterns, app-accessibility, app-performance |
| Storefront or theme work | storefront-api, hydrogen-storefront, or liquid-themes |
metafields-metaobjects |
| Checkout or backend customization | shopify-functions |
admin-graphql, dev-troubleshooting |
| Webhook delivery or signature verification | webhooks |
app-auth, dev-troubleshooting |
| Pre-ship or App Store review | built-for-shopify-standards |
merchant-pain-prevention, app-accessibility, app-performance, UX skills |
| Listing, name, price, or market validation | app-listing-optimization, app-naming, app-pricing-strategy, or app-validation |
app-niche-finder |
| App Store advertising | shopify-app-store-ads |
app-listing-optimization, app-pricing-strategy |
| Shopify MCP or agentic commerce | shopify-mcp |
Relevant API and authentication skills |
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 · 59 lines · 100 tokens per session scan A 47bc2b2c297a
using-shopify-app-builder is a skill published in the GitHub repository khadinakbarlabs/shopify-app-builder (1 stars, last pushed 1mo ago), licensed MIT. It adds 100 tokens to every session and 975 once invoked, about $0.0005 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.