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.
git clone --depth 1 https://github.com/jameywarren/shopify-claude-quickstartWrote 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/commands/jameywarren/shopify-claude-quickstart/launch-checklist)<a href="https://agentmods.dev/commands/jameywarren/shopify-claude-quickstart/launch-checklist"><img src="https://agentmods.dev/badge/commands/jameywarren/shopify-claude-quickstart/launch-checklist/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/commands/jameywarren/shopify-claude-quickstart/launch-checklist"><img src="https://agentmods.dev/badge/commands/jameywarren/shopify-claude-quickstart/launch-checklist.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.00017 | $0.00782 |
| Opus 5 | $0.00009 | $0.00391 |
| Sonnet 5 | $0.00003 | $0.00156 |
| Haiku 4.5 | $0.00002 | $0.00078 |
Grade A, and why
launch-checklist 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run a systematic pre-launch check. For each area, determine pass/fail by querying the store or reading the brief. Flag anything that blocks going live.
Read first:
client-brief/business-goals.md— target apps, constraints, launch datestore-data/store-profile.md— installed apps, store configdocs/session-log.md— what was done this build
Use shopify-plugin:shopify-admin-execution for queries (read-only throughout).
1. Payments
- Is a payment provider connected and not in test mode?
- Does checkout accept a test order end-to-end?
- Are payment methods correct for the target market?
2. Domain & SSL
- Is the custom domain connected and DNS propagated?
- Is www → apex (or apex → www) redirect configured?
- Is SSL active?
- Is the storefront password removed?
3. Theme
- Is the correct theme published as the live theme?
- Run
/safe-pushto confirm the live theme passed its pre-flight. - Are dev/backup themes labeled and not cluttering the theme list?
4. Email Notifications
- Have transactional templates been customized? (Order confirmation, shipping notification at minimum.)
- Do they match the brand voice in
client-brief/voice-style-guide.md? - Is the sender email a domain-verified address (not the default Shopify relay)?
5. Redirects
- Are all redirects from
client-brief/navigation.md(SEO Notes) live? - Verify the 3 most critical old URLs return 301s, not 404s.
- If redirects haven't been built yet, run
/redirect-buildnow.
6. Legal Pages
- Privacy Policy published and linked in the footer?
- Refund Policy published?
- Shipping Policy and Terms of Service present if required by the market?
Check that these aren't still Shopify placeholder text — query pages for these handles and flag if body is under 200 characters.
7. Shipping
- Shipping zones configured for all target markets?
- Rates match what was agreed (free over threshold, calculated, flat)?
- Test order reaches checkout with the correct shipping option displayed?
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 · 102 lines · 17 tokens per session scan A b63749f75826
launch-checklist is a command published in the GitHub repository jameywarren/shopify-claude-quickstart (2 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 782 once invoked, about $0.0001 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 commands, from other repositories
dev
Runs Vendure in development mode. By default it starts three processes: the GraphQL server (ts-node ./src/index.ts), the worker (ts-node ./src/index-worker.ts), and the dashboard (a Vite dev server).
start
Runs a project that has already been compiled with vendure build.
validate-idea
Validate Shopify app idea against market demand, category saturation, App Store discovery patterns, and monetization viability.
ebay-orders
Check recent eBay orders and fulfillment status.
intake
You are running the intake for this purchase. The goal is to populate spec.md at the repo root with the per-purchase brief.
price-strategy
You are a senior E-commerce & Retail specialist. The user needs help with price strategy in the context of product catalogue optimisation, conversion rate, customer journey and retail analytics.