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/design-intake)<a href="https://agentmods.dev/commands/jameywarren/shopify-claude-quickstart/design-intake"><img src="https://agentmods.dev/badge/commands/jameywarren/shopify-claude-quickstart/design-intake/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/design-intake"><img src="https://agentmods.dev/badge/commands/jameywarren/shopify-claude-quickstart/design-intake.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.00012 | $0.00755 |
| Opus 5 | $0.00006 | $0.00378 |
| Sonnet 5 | $0.00002 | $0.00151 |
| Haiku 4.5 | $0.00001 | $0.00076 |
Grade A, and why
design-intake 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are turning a visual design into a buildable Shopify implementation plan. Design decisions are already made — your job is to translate them into theme-specific implementation specs, flag what can't be built natively, and save the output so future sessions don't have to re-derive it.
Page: $ARGUMENTS (default: homepage if not specified)
Step 1 — Gather inputs
Read everything relevant before asking questions:
design/mockups/— look for images matching the page namedesign/brand-system.md— palette, fonts, voicedesign/page-specs/— check if a spec already exists for this pageclient-brief/design-brief.md(orclient-brief-QUICK.md)store-data/theme/sections/andstore-data/theme/blocks/— what sections exist
Then ask only what you can't answer from the files:
- If no mockup is visible in
design/mockups/, ask: "Do you have a design file or mockup to share? Drop it in design/mockups/ and tell me the filename, or describe the layout." - "Are SVG assets (wordmark, icons) available in
design/assets/?" - "Are fonts already loaded in the theme, or do they need to be added?"
Don't ask about things you can already see in the brief or brand system.
Step 2 — Module inventory
Identify every distinct visual module in the design (e.g. nav, hero, featured collections, text+image, newsletter, footer). For each module:
| Module | Design intent | Theme section to use | Fit | Gap |
|---|---|---|---|---|
| Hero | Full-bleed image, headline, CTA | sections/hero-banner.liquid |
Native | None |
| ... |
Fit ratings:
- Native — the theme section does this out of the box
- Configure — native section but needs specific settings or schema additions
- Modify — closest native section requires Liquid edits
- Custom — no native section can do this; new section required
Flag every "Modify" or "Custom" upfront. These are build-time decisions.
Step 3 — Per-module implementation spec
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 · 70 lines · 12 tokens per session scan A 997cd37d99c6
design-intake is a command published in the GitHub repository jameywarren/shopify-claude-quickstart (2 stars, last pushed 4mo ago), licensed MIT. It adds 12 tokens to every session and 755 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
checkout-specialist
Use when a cart or checkout is losing people. Abandoned carts, long payment forms, forced account creation, shipping cost revealed too late, weak trust signals, confusing order confirmation.
ux-grill
You are a senior E-commerce & Retail specialist applying E-commerce Engineering Skills methodology.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
p3-ux-wireframes
Creates wireframes (ASCII art) for the most important screens with interaction descriptions.
4-generate
Run Stage 4 of the design system skill generation pipeline: parallel skill file generation.
mockups-generate
Generate dashboard mockups.