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/homepage-from-brief)<a href="https://agentmods.dev/commands/jameywarren/shopify-claude-quickstart/homepage-from-brief"><img src="https://agentmods.dev/badge/commands/jameywarren/shopify-claude-quickstart/homepage-from-brief/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/homepage-from-brief"><img src="https://agentmods.dev/badge/commands/jameywarren/shopify-claude-quickstart/homepage-from-brief.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.00013 | $0.00388 |
| Opus 5 | $0.00006 | $0.00194 |
| Sonnet 5 | $0.00003 | $0.00078 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
homepage-from-brief 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 11d 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.
What it actually says
First, check design/ for existing design artifacts:
- If
design/page-specs/homepage.mdexists — implementation decisions are already made. Use that spec as the source of truth and skip layout proposal. Go straight to mapping each module to the right theme section. - If
design/mockups/has a homepage image — treat it as design direction. Run/design-intake homepagefirst, then come back to implement. - If
design/brand-system.mdis filled in — use it for all color, font, and voice decisions; it overrides the client brief for visual choices. - If
design/is empty — proceed from the brief, but flag at the end that no visual design direction has been captured yet and suggest running/brand-systembefore implementation.
Then read:
client-brief/design-brief.mdclient-brief/page-content.mdclient-brief/business-goals.mdclient-brief/voice-style-guide.md- (or
client-brief-QUICK.mdif the full brief isn't filled in) store-data/theme-sections.mdif it exists, otherwisestore-data/theme/sections/
Propose a homepage layout using only sections that exist in the pulled theme. For each section:
- Which section file to use (e.g.,
sections/hero.liquid) - Why this section vs alternatives in the theme
- Exact settings to configure
- Content to populate from the brief
- Order in the template
Do not suggest custom sections unless no native section can do the job — and if you do, explain explicitly why.
Flag content gaps where the client needs to provide assets or copy. End with the recommended sequence to actually build it (which command/mutation runs first).
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.
- 11d ago First seen · 31 lines · 13 tokens per session scan A 6ea02bfda868
homepage-from-brief 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 388 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.