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 agentmods add commands/jameywarren/shopify-claude-quickstart/implement-mockup-modulegit 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/implement-mockup-module)<a href="https://agentmods.dev/commands/jameywarren/shopify-claude-quickstart/implement-mockup-module"><img src="https://agentmods.dev/badge/commands/jameywarren/shopify-claude-quickstart/implement-mockup-module.svg" alt="Measured on agentmods" 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.00013 | $0.00576 |
| Opus 5 | $0.00006 | $0.00288 |
| Sonnet 5 | $0.00003 | $0.00115 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade A, and why
implement-mockup-module 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 5d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are implementing one module from a finalized design. Design decisions are already made — your job is translation, not proposal.
Module: $ARGUMENTS
If no module name was provided, list the files in design/ and ask which one to implement.
Step 1 — Read the design artifact
Look in design/ for files matching the module name (e.g., design/hero.*, design/hero/). This may be:
- An image (
.png,.jpg,.webp) — read it visually - A spec file (
.md,.txt,.json) — read the contents - A folder — read everything inside
Also read:
client-brief/design-brief.md(orclient-brief-QUICK.md) for colors, fonts, spacing intentclient-brief/voice-style-guide.mdfor any copy in the module
Step 2 — Identify the matching theme section
Scan store-data/theme/sections/ and store-data/theme/blocks/ for the section(s) that best implement this module. State:
- Which section file you're using and why
- Whether it's a native fit, a close fit, or a stretch — be honest
- If it's a stretch: what gap exists and whether a schema addition can close it vs. requiring custom code
Do not propose a new custom section unless no native section can do the job. If you must, say so explicitly.
Step 3 — Output the implementation
Produce three things:
1. Settings mapping — a table or annotated list: design element → section setting → value. Every visible design decision should map to a named setting.
2. JSON settings block — the exact JSON for this section in templates/index.json, ready to paste or upsert. Use real values from the design, not placeholders.
3. Upsert mutation — validated by shopify-plugin:shopify-admin, ready to run:
shopify store execute --store {STORE}.myshopify.com --allow-mutations \
--query 'mutation themeFilesUpsert(...) { ... }'
Show the mutation but do not execute until confirmed.
Step 4 — Flag gaps
List anything that blocks clean execution:
- Images referenced in the design that aren't yet uploaded to Shopify Files
- Copy the client still needs to provide
- Settings the section schema doesn't support (and whether a schema addition is needed)
- Any ordering dependency (e.g., this section must come after another)
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.
- 5d ago First seen · 58 lines · 13 tokens per session scan A c0785aff0345
implement-mockup-module is a command published in the GitHub repository jameywarren/shopify-claude-quickstart (2 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 576 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.