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/recover-context)<a href="https://agentmods.dev/commands/jameywarren/shopify-claude-quickstart/recover-context"><img src="https://agentmods.dev/badge/commands/jameywarren/shopify-claude-quickstart/recover-context/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/recover-context"><img src="https://agentmods.dev/badge/commands/jameywarren/shopify-claude-quickstart/recover-context.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.00010 | $0.00578 |
| Opus 5 | $0.00005 | $0.00289 |
| Sonnet 5 | $0.00002 | $0.00116 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade A, and why
recover-context 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 10d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stop. Work through these steps in order before proposing anything.
Step 1 — Check git availability
git rev-parse --is-inside-work-tree 2>/dev/null && echo "git:yes" || echo "git:no"
Step 2 — Reconstruct recent history
If git is available, run both:
git log --oneline -15
git diff HEAD~1 --stat
This gives a timestamped timeline of every push and session commit, plus exactly what changed last session. Read this before touching any prose files.
If git is not available, skip to Step 3.
If both git and docs/session-log.md exist, use both — git for the timeline and exact diffs, session-log for narrative context and open questions that don't show up in diffs.
Step 3 — Re-read project state
- Re-read
CLAUDE.mdcompletely — store handle, active theme, current build phase - Re-read
docs/session-log.mdif it exists — last 3 entries minimum. The most recent "Next Session: Start Here" is the first action.
Step 4 — Load store data from local snapshots
Check which of these files exist and read them. Do not re-query the API if local data is available:
store-data/store-profile.md— store config, installed apps, theme detailsstore-data/pages.json— all pages and handlesstore-data/navigation.json— menu structurestore-data/collections.json— collection handles and rulesstore-data/products-index.csv— product handles, titles, types, collectionsstore-data/metafield-definitions.json— defined metafields by owner typestore-data/theme-sections.md— section inventory
If none of these snapshots exist yet, note that and suggest running /pull-store-data after auth is confirmed.
Step 5 — Verify auth
Run /check-auth to confirm the store session is live. If auth has lapsed, re-authenticate. Do not run /init-store — that is a first-session-only command.
Step 6 — Report orientation
Tell me:
- What store and theme are we working on?
- What were we in the middle of? (from git log and/or session log)
- What changed last session? (from git diff or session log)
- What's the next concrete step?
- Is local store data fresh enough, or does
/pull-store-dataneed to run?
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.
- 10d ago First seen · 75 lines · 10 tokens per session scan A f1eba099034b
recover-context is a command published in the GitHub repository jameywarren/shopify-claude-quickstart (2 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 578 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
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.