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 shopify-app-store-adsgit 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/shopify-app-store-ads)<a href="https://agentmods.dev/skills/khadinakbarlabs/shopify-app-builder/shopify-app-store-ads"><img src="https://agentmods.dev/badge/skills/khadinakbarlabs/shopify-app-builder/shopify-app-store-ads/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/shopify-app-store-ads"><img src="https://agentmods.dev/badge/skills/khadinakbarlabs/shopify-app-builder/shopify-app-store-ads.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.00086 | $0.01931 |
| Opus 5 | $0.00043 | $0.00966 |
| Sonnet 5 | $0.00017 | $0.00386 |
| Haiku 4.5 | $0.00009 | $0.00193 |
Grade A, and why
shopify-app-store-ads 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shopify App Store Ads
Use App Store ads to test qualified merchant acquisition, not to buy superficial installs. Treat the Shopify Partner Dashboard and current Shopify documentation as the authority for eligibility, available placements, bid behavior, billing, and reporting.
Ground Rules
- Verify that the app is publicly published and eligible before proposing launch. An active development version is not evidence of a public App Store listing or advertising eligibility.
- Research live platform rules before acting. Start with Shopify's App Store ads documentation, then verify the visible Partner Dashboard controls for the specific app.
- Use community sources (Reddit, reviews, founder posts) to form keyword, pain-point, and creative hypotheses. Label them as anecdotal; do not present them as Shopify policy or benchmark data.
- Never create, enable, or materially raise a paid campaign without the user's explicit confirmation of the currency, daily cap, total test cap, and stop date. Do not infer approval from a request to "run ads."
- Never call a campaign live from an API response, draft state, or local configuration alone. Confirm its visible dashboard status, targeting, budget, billing readiness, and landing/listing preview.
- Do not promise customers or return on ad spend before enough cohort time has passed. Distinguish clicks, installs, trials, activated merchants, and paid customers.
Readiness Gate
Collect these facts before recommending spend:
- Public App Store listing URL, app status, category, supported geographies, and current price/trial terms.
- Listing conversion evidence: title, tagline, screenshots, review count/rating, pricing clarity, and a merchant-facing promise that matches the target query.
- A working install-to-value path: first-run activation event, billing/trial event, and paid-conversion event. Name the exact analytics source and event names; do not invent them.
- Unit economics: monthly plan(s), gross margin, expected paid retention, acceptable payback window, and the maximum customer-acquisition cost (CAC).
- Partner account access, ad billing readiness, and the person authorized to approve spend.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 140 lines · 86 tokens per session scan A cafa9124c9a9
shopify-app-store-ads is a skill published in the GitHub repository khadinakbarlabs/shopify-app-builder (1 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 1,931 once invoked, about $0.0004 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.