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/general-search)<a href="https://agentmods.dev/commands/danielrosehill/claude-israel-shopping-plugin/general-search"><img src="https://agentmods.dev/badge/commands/danielrosehill/claude-israel-shopping-plugin/general-search/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/general-search"><img src="https://agentmods.dev/badge/commands/danielrosehill/claude-israel-shopping-plugin/general-search.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.00060 | $0.00665 |
| Opus 5 | $0.00030 | $0.00332 |
| Sonnet 5 | $0.00012 | $0.00133 |
| Haiku 4.5 | $0.00006 | $0.00067 |
Grade A, and why
general-search 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 11d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
General Search
Cross-retailer Israeli search covering tier-2 majors (Ace, Home Center, Office Depot, Audioline), Google IL discovery, and category-dispatched sweeps of the merged store list for niche specialists.
See
docs/search-strategies.mdfor the tier-2 retailer table, Google IL query patterns, category-dispatch vocabulary, Hebrew-term resolution, and store-metadata merge convention.
When to use
- Product leans household / office / appliance / audio rather than pure consumer tech.
- Tier-1 tech search (
/tech-product-search) and Zap came back empty. - Niche specialist categories — tactical, lighting, photography, gaming, smart home.
- Discovery-mode queries where no specific retailer is in mind.
For most cross-retailer price comparison, try /search-zap first. Come here when Zap misses or for broader discovery.
Workflow
- Classify the query — does it fit tier-2 majors, a niche category, or does it need Google discovery?
- Resolve Hebrew term (preflight — see strategies doc).
- Load the merged store list — upstream
stores.jsonoverlaid with<plugin-data-dir>/user-stores.json (resolved via $CLAUDE_USER_DATA — see docs/search-strategies.md)(see strategies doc). - Pick path:
- Tier-2 majors — search Ace, Home Center, Office Depot, Audioline via Playwright homepage form or Tavily.
- Category-dispatch — filter merged store list by matching
categories[]; pick up to 8 stores; search each. - Google IL — patterns from strategies doc (
"brand model" site:.il,מחיר <hebrew>, Google Shopping IL).
- Rank low-to-high by VAT-inclusive ILS price. Cap 5 per retailer / 3 per niche store.
- Flag retailers not in the merged store list — candidates for
/add-store.
Output
## {product} — general IL search
Hebrew query: {hebrew}
Path: {tier-2 | category:{cats} | google-il | mixed}
Stores/sources searched: {n}
| # | ₪ (inc. VAT) | Product | Retailer | Link |
|---|---|---|---|---|
### Notes
- Retailers not in merged store list (candidates to add): ...
- Retailers that returned nothing / errored: ...
- Out-of-category misses: ...
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.
- 11d ago First seen · 56 lines · 60 tokens per session scan A f8b0c1dc6463
general-search is a command published in the GitHub repository danielrosehill/Claude-Israel-Shopping-Plugin (3 stars, last pushed 4mo ago), licensed MIT. It adds 60 tokens to every session and 665 once invoked, about $0.0003 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.