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 dev-troubleshootinggit 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/dev-troubleshooting)<a href="https://agentmods.dev/skills/khadinakbarlabs/shopify-app-builder/dev-troubleshooting"><img src="https://agentmods.dev/badge/skills/khadinakbarlabs/shopify-app-builder/dev-troubleshooting/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/dev-troubleshooting"><img src="https://agentmods.dev/badge/skills/khadinakbarlabs/shopify-app-builder/dev-troubleshooting.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.00175 | $0.10758 |
| Opus 5 | $0.00088 | $0.05379 |
| Sonnet 5 | $0.00035 | $0.02152 |
| Haiku 4.5 | $0.00017 | $0.01076 |
Grade A, and why
dev-troubleshooting 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 — 828 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shopify Dev Troubleshooting — Triage First, Fix Fast
A symptom-driven triage skill for Shopify app developers. When your dev loop hits a wall, start here. Each pain below is sourced from the most-reported Reddit, Shopify Developer Community (community.shopify.dev), Shopify Community (community.shopify.com), and GitHub Shopify/* issues as of 2026-05-15.
Use this skill first when:
shopify app devexits with cryptic errors- The browser shows "No AppBridge context provided", 401, 302 loops, or 404 on
/auth/login - GraphQL "works" but data is missing in production
- Webhooks fire twice, never, or your handler keeps timing out
- A Function deploys fail with
[wasm-validator error] - App Review SLA is blown and you don't know what to do
- A dev-store billing test charge silently fails
If the symptom matches a row in the Diagnostic Table, jump straight to that fix. If not, work through the Decision Tree at the bottom.
1. When to Use This Skill
This is the entry point for any "something is broken in my Shopify dev workflow" question. It is not the place to learn how to build new features — that's what the other shopify-app-builder skills are for. This skill is the ER, not the gym.
Surface this skill when the user says any of:
- "shopify app dev failing / not working / errors"
- "tunnel won't start", "cloudflared", "max retries reached"
- "App Bridge migration", "v3 to v4", "No AppBridge context provided"
- "graphql throttled", "200 OK error", "currentlyAvailable"
- "webhook 401", "double webhook", "duplicate webhook", "webhook retry"
- "remix auth broken", "/auth/login 404", "nested route login"
- "wasm-validator error", "wasm-opt failed", "Rust function deploy"
- "session token expired", "24 hour", "iframe redirect blocked"
- "X-Frame-Options", "frame-ancestors", "DENY"
- "billing test charge", "Apps without public distribution"
- "app review", "Built for Shopify rejected", "SLA blown"
- "shopify cli error", "cannot read properties of null"
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 · 828 lines · 175 tokens per session scan A 75b1ad65cdaa
dev-troubleshooting is a skill published in the GitHub repository khadinakbarlabs/shopify-app-builder (1 stars, last pushed 29d ago), licensed MIT. It adds 175 tokens to every session and 10,758 once invoked, about $0.0009 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
debugging
Runs a hypothesis-driven debugging loop across any language or binary, escalating to orthogonal oracle angles and locking the fix with a failing test. Use for crashes, silent failures, hangs, wrong responses, memory leaks, async misbehavior, or reverse engineering.
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.
ast-grep
Searches and rewrites code by AST shape across 25 languages. Use when the target is a syntax pattern (every call/class/import shaped like X, a codemod, a YAML rule) rather than literal text; for plain strings, comments, or filenames, use rg.
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits. Triggers: remove dead code, dead code, cleanup, remove unused.
lcx-doctor
Diagnose LazyCodex and Codex CLI installation health against the latest sources. Use whenever the user asks for a doctor or health check, says LazyCodex, lazycodex-ai, omo-codex, or Codex behaves oddly after an install, update, or config change, suspects a stale, drifted, or broken setup, or wants the local install…
lsp
Use when Codex needs language-server diagnostics, definitions, references, symbols, or rename safety checks in the current workspace.