A one-time setup process for a new Shopify store, including access, a copy of the theme, an audit, and project notes. Shopify is the platform that runs the store, while a theme contains its storefront design and code.

Use it to authenticate for the required store areas, pull the theme, inspect the store, and fill in CLAUDE.md with useful context for future sessions.

It gives the project a known starting point and records the store’s structure, data, and working rules before development begins.

init-store — Command for Claude Code by jameywarren

Install

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.

Clone the repo

git clone --depth 1 https://github.com/jameywarren/shopify-claude-quickstart

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/jameywarren/shopify-claude-quickstart/init-store/github.svg)](https://agentmods.dev/commands/jameywarren/shopify-claude-quickstart/init-store)

Your own site

<a href="https://agentmods.dev/commands/jameywarren/shopify-claude-quickstart/init-store"><img src="https://agentmods.dev/badge/commands/jameywarren/shopify-claude-quickstart/init-store/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/jameywarren/shopify-claude-quickstart/init-store"><img src="https://agentmods.dev/badge/commands/jameywarren/shopify-claude-quickstart/init-store.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,604 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.01604
Opus 5.5	$0.00007	$0.00642
Sonnet 5.5	$0.00003	$0.00321
Haiku 4.5	$0.00002	$0.00160

Measured 1mo ago against content hash 4ce2e87dd9a4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

init-store 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 1mo 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.

.claude/commands/init-store.md · 129 lines

How it starts

The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are running the first-session setup for a new Shopify store. Do all of the following in order. After each step, briefly report what happened.

Store handle: $ARGUMENTS

If no store handle was provided, ask the user for it before proceeding.

Step 1 — Authenticate with the full scope set

Use shopify-plugin:shopify-admin-execution. Run:

shopify store auth --store {STORE}.myshopify.com --scopes \
  read_themes,write_themes,\
read_products,write_products,\
read_content,write_content,\
read_metaobjects,write_metaobjects,\
read_metaobject_definitions,write_metaobject_definitions,\
read_files,write_files,\
read_script_tags,write_script_tags,\
read_price_rules,write_price_rules,\
read_inventory,write_inventory,\
read_customers,read_orders,\
read_locations

Scope notes (verified 2026-04):

read_metafield_definitions / write_metafield_definitions — NOT valid scopes. Metafield access is gated by the owning resource (e.g. read_products covers product metafields).

read_metafields / write_metafields — NOT valid scopes. Same story.

read_navigation / write_navigation — NOT valid scopes. Navigation menus are covered by read_content / write_content.

read_apps — DO NOT include. It is a protected scope requiring special Partner Dashboard approval. Including it in the scope list causes OAuth to fail for the entire auth request with missing_shopify_permission: read_apps. App data can be retrieved by asking the client to list their installed apps from the Shopify admin.

read_locations is required for any locations query.

OAuth will reject the entire scope list if any single scope is invalid or unapproved, so one bad scope blocks all auth.

Then update store-data/scopes-granted.md — record store handle, today's date, and mark each scope Granted: Y.

Step 2 — Pull the current theme

shopify theme pull uses your Shopify Partner account login, not the shopify store auth session. You must have collaborator or staff access to the store before this step will work.

Read the full file on GitHub · 129 lines

Changes

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.

1mo ago First seen · 129 lines · 17 tokens per session scan A 4ce2e87dd9a4

Subscribe to this mod's changes

init-store is a command published in the GitHub repository jameywarren/shopify-claude-quickstart (2 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 1,604 once invoked, about $0.0001 per session on Opus 5.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.

E-commerce

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).

vendurehq/vendure · 0 tokens

start

Runs a project that has already been compiled with vendure build.

vendurehq/vendure · 0 tokens

sync-medusa-docs-changes

You are a technical maintainer of the medusajs/medusa-agent-skills repository, which publishes Claude Code plugins whose skill files restate Medusa documentation as instructions for a coding agent. You read documentation diffs and judge whether they make any published instruction wrong.

medusajs/medusa-agent-skills · 0 tokens

init-store