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/danielrosehill/Claude-Israel-Shopping-PluginWrote 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/danielrosehill/claude-israel-shopping-plugin/add-store)<a href="https://agentmods.dev/commands/danielrosehill/claude-israel-shopping-plugin/add-store"><img src="https://agentmods.dev/badge/commands/danielrosehill/claude-israel-shopping-plugin/add-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.
<a href="https://agentmods.dev/commands/danielrosehill/claude-israel-shopping-plugin/add-store"><img src="https://agentmods.dev/badge/commands/danielrosehill/claude-israel-shopping-plugin/add-store.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.00041 | $0.00935 |
| Opus 5 | $0.00020 | $0.00467 |
| Sonnet 5 | $0.00008 | $0.00187 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
add-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 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Store
Append a new Israeli retailer to the user's persistent store overlay. Does not modify the upstream stores.json or anything inside the plugin install directory — those get clobbered on update.
Migration from legacy path (one-time)
Before resolving the data directory, check for legacy data at these paths:
<plugin-data-dir>/user-stores.json
If a legacy file exists AND the corresponding file at the new path does NOT exist, move it to the new location (creating the parent directory as needed) and delete the legacy file (plus the empty <plugin-data-dir>/ directory). Tell the user: "Migrated user-stores.json from / to ."
Path resolution
Resolve the plugin's data directory as $CLAUDE_USER_DATA/israel-shopping/ if CLAUDE_USER_DATA is set; otherwise $XDG_DATA_HOME/claude-plugins/israel-shopping/ if XDG_DATA_HOME is set; otherwise ~/.local/share/claude-plugins/israel-shopping/. Create the directory if it doesn't exist. See the canonical convention in the meta-tools:plugin-data-storage skill.
Shell form:
PLUGIN_DATA_DIR="${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/israel-shopping"
mkdir -p "$PLUGIN_DATA_DIR"
Referred to below as <plugin-data-dir>/.
Arguments
$ARGUMENTS: <url> "<what they sell>" [--name "Display Name"] [--is-tech true|false|null]
Storage
User additions go to:
<plugin-data-dir>/user-stores.json
Create the parent directory if missing. File is a JSON array of store entries whose shape matches the upstream stores.json. To confirm the current schema, fetch a live entry:
https://raw.githubusercontent.com/danielrosehill/Israel-Online-Stores/main/stores.json
and use the same field names and types.
Consumer commands (
/tech-product-search,/general-search,/store-zap-lookup, etc.) load the upstream list first and overlayuser-stores.jsonon top — seedocs/search-strategies.md§ store-metadata merge convention.
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 · 86 lines · 41 tokens per session scan A 21ea49853fd5
add-store is a command published in the GitHub repository danielrosehill/Claude-Israel-Shopping-Plugin (3 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 935 once invoked, about $0.0002 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
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).
start
Runs a project that has already been compiled with vendure build.
validate-idea
Validate Shopify app idea against market demand, category saturation, App Store discovery patterns, and monetization viability.
intake
You are running the intake for this purchase. The goal is to populate spec.md at the repo root with the per-purchase brief.
price-strategy
You are a senior E-commerce & Retail specialist. The user needs help with price strategy in the context of product catalogue optimisation, conversion rate, customer journey and retail analytics.
price-strategy
You are a senior E-commerce & Retail specialist. The user needs help with price strategy in the context of product catalogue optimisation, conversion rate, customer journey and retail analytics.