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/github-setupgit clone --depth 1 https://github.com/jameywarren/shopify-claude-quickstartWhat 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.00017 | $0.00821 |
| Opus 5 | $0.00009 | $0.00411 |
| Sonnet 5 | $0.00003 | $0.00164 |
| Haiku 4.5 | $0.00002 | $0.00082 |
Grade A, and why
github-setup 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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up GitHub tracking for this project. Work through the steps below in order. At each step, report what happened before continuing.
Step 1 — Initialize git (if not already done)
Check if this directory is already a git repo:
git rev-parse --is-inside-work-tree 2>/dev/null && echo "yes" || echo "no"
If not initialized:
git init && git checkout -b main
Step 2 — Verify the .gitignore is correct
Read .gitignore and confirm it contains the binary asset rules (.png, .jpg, .woff, etc. inside store-data/theme/assets/). These large files should not be committed — Shopify hosts them.
If the rules are missing, add them now before committing anything.
Step 3 — Initial commit
Stage and commit all project files:
git add -A
git status
Show me the staged file list. If it looks right (theme Liquid/JSON files, CLAUDE.md, commands, briefs — no large binaries), commit:
git commit -m "init: pulled theme + project scaffold
Theme pulled from Shopify. Project ready for build.
Co-Authored-By: Claude Sonnet 4.6 <[email protected]>"
Step 4 — Create the GitHub repo
Check if the GitHub CLI (gh) is installed:
gh --version 2>/dev/null && echo "available" || echo "not found"
If gh is available:
Check if already authenticated:
gh auth status 2>&1
If not authenticated, tell the user:
"You'll need to log in to GitHub. Run
gh auth loginin your terminal — choose GitHub.com, then HTTPS or SSH based on your preference, and follow the prompts."
Wait for confirmation before continuing.
Once authenticated, create a private repo and push:
gh repo create {STORE-HANDLE}-shopify --private --source=. --remote=origin --push
Replace {STORE-HANDLE} with the actual store handle (e.g. danbaileys-shopify).
Report the repo URL when done.
If gh is not available:
Tell the user:
Option A — Install the GitHub CLI (recommended):
- Go to cli.github.com and install
ghfor your OS- Run
gh auth loginand follow the prompts- Come back and run
/github-setupagainOption B — Create the repo manually on GitHub:
- Go to github.com/new
- Name it
{STORE-HANDLE}-shopify(e.g.danbaileys-shopify)- Set it to Private
- Do not initialize with a README, .gitignore, or license — the project already has these
- Click Create repository
- Copy the repo URL (HTTPS or SSH)
- Tell me the URL and I'll connect it
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 · 118 lines · 17 tokens per session scan A 6ad81c1e9a9e
github-setup is a command published in the GitHub repository jameywarren/shopify-claude-quickstart (2 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 821 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
speckit.git.commit
Auto-commit changes after a Spec Kit command completes.
commit-all
Group all changes semantically and commit each group separately.
commit
Based on the above changes, create a single git commit.
commit
Safe git commit practices for MindRoom.
commit
智能生成 Git 提交信息并提交.
commit
Create a Conventional Commit with signoff.