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/toolkit-update)<a href="https://agentmods.dev/commands/jameywarren/shopify-claude-quickstart/toolkit-update"><img src="https://agentmods.dev/badge/commands/jameywarren/shopify-claude-quickstart/toolkit-update/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/toolkit-update"><img src="https://agentmods.dev/badge/commands/jameywarren/shopify-claude-quickstart/toolkit-update.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.00015 | $0.00344 |
| Opus 5 | $0.00008 | $0.00172 |
| Sonnet 5 | $0.00003 | $0.00069 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
toolkit-update 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 8d 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, detect which setup you're in by running:
git remote -v
Then follow the matching path:
If upstream remote exists (Path B — cloned template directly, remapped remotes):
git fetch upstream
git merge upstream/main
If there are merge conflicts, they'll most likely be in CLAUDE.md (which you've customized for your store). Resolve them manually — keep your STORE DETAILS and THEME NOTES, take the upstream version of everything else.
If origin points to shopify-claude-quickstart (working inside the template repo itself):
git pull origin main
If neither applies (client directory scaffolded via setup.sh):
Client directories are standalone snapshots — they have no link back to the template. You can't pull updates into them automatically.
To get improvements into a client project, open the shopify-claude-quickstart/ source directory in a separate Claude Code session and run /toolkit-update there. Then manually port any changes that matter (new commands, CLAUDE.md additions) into the client directory.
Alternatively, re-read the README for the fork-with-upstream setup that keeps a client directory in sync.
After a successful pull, summarize what changed:
- New slash commands added
- Changes to CLAUDE.md that affect session behavior
- Changes to setup.sh
- Any breaking changes to existing commands
3–5 bullets. If nothing changed beyond minor fixes, say so.
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.
- 8d ago First seen · 51 lines · 15 tokens per session scan A 2d22323e5def
toolkit-update is a command published in the GitHub repository jameywarren/shopify-claude-quickstart (2 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 344 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
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
handoff
Export a Waybill Bundle by default, or import one when requested.