What is setup-local-dev?

A command that checks and configures the local environment for a Shopify embedded app, an app that runs inside Shopify's admin or storefront tools.

Checking Docker, Node.js, Shopify CLI, dependencies, and required files; starting local DynamoDB and LocalStack services; and creating the environment file when needed.

It catches missing tools, dependencies, services, or configuration that could prevent local development from starting.

setup-local-dev — Command by mentilead

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.

agentmods

npx agentmods add commands/mentilead/shopify-app-skill/setup-local-dev

Clone the repo

git clone --depth 1 https://github.com/mentilead/shopify-app-skill

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

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

Security scan A 0 findings. Scan, not verified.

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	$0.00000	$0.00523
Opus 5	$0.00000	$0.00262
Sonnet 5	$0.00000	$0.00105
Haiku 4.5	$0.00000	$0.00052

Measured 2d ago against content hash 71274a7203d1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

setup-local-dev 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 2d 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.

commands/setup-local-dev.md · 42 lines

How it starts

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

Setup Local Dev

Verify and configure the local development environment for a Shopify embedded app.

Arguments

$ARGUMENTS = optional flags (e.g., "reset" to start fresh, "check" to only verify without changes)

Instructions

Read .claude/skills/shopify-app/references/local-dev-patterns.md for Docker Compose setup, startup sequence, and environment variables.
Read .claude/skills/shopify-app/SKILL.md for key environment variables table and gotcha #10 (cached store association).
Run pre-flight checks:
- Verify Docker is installed and running: docker info
- Verify Node.js version matches requirements: node --version
- Verify Shopify CLI is installed: shopify version
- Verify npm dependencies are installed: check node_modules/ exists
- Check if docker-compose.yml exists in the project root
If $ARGUMENTS contains "check", report the status of each check and stop. Do not make changes.
Start infrastructure services:
- Run docker compose up -d to start DynamoDB Local, DynamoDB Admin, and LocalStack
- Wait for services to be healthy: check ports 8000 (DynamoDB), 8001 (Admin), 4566 (LocalStack)
Set up the .env file if it doesn't exist:
- Copy from .env.example if available
- Ensure these local development values are set:
  - DYNAMODB_ENDPOINT=http://localhost:8000
  - AWS_S3_ENDPOINT=http://localhost:4566
  - EMAIL_QUEUE_URL pointing to LocalStack SQS
- Ask the user for SHOPIFY_API_KEY and SHOPIFY_API_SECRET if not set
Create the DynamoDB table if it doesn't exist:
- Run npm run setup or the table creation script
- Verify the table was created via DynamoDB Admin at http://localhost:8001
If $ARGUMENTS contains "reset":
- Warn the user this will delete local data
- Run docker compose down -v to remove volumes
- Restart from step 5
Report the final status:
- List all running services and their ports
- Confirm .env is configured
- Confirm DynamoDB table exists
- Print the next step: shopify app dev to start the app

Read the full file on GitHub · 42 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.

2d ago First seen · 42 lines · 0 tokens per session scan A 71274a7203d1

Subscribe to this mod's changes

setup-local-dev is a command published in the GitHub repository mentilead/shopify-app-skill (5 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 523 tokens. 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 aws-cdk aws-lambda claude-code claude-code-skill dynamodb embedded-app

setup-local-dev

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Setup Local Dev

Arguments

Instructions

What this file has done since we first saw it

Other commands, from other repositories

thread

dev

cti-report

ask

setup

zuora-cpq-migration-design