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/mrjptech/macro-pickle/pickle-winnersgit clone --depth 1 https://github.com/MrJPTech/macro-pickleWrote 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/mrjptech/macro-pickle/pickle-winners)<a href="https://agentmods.dev/commands/mrjptech/macro-pickle/pickle-winners"><img src="https://agentmods.dev/badge/commands/mrjptech/macro-pickle/pickle-winners.svg" alt="Measured on agentmods" 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.00020 | $0.00449 |
| Opus 5 | $0.00010 | $0.00225 |
| Sonnet 5 | $0.00004 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
pickle-winners 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 5d 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
/pickle-winners
Rank a store's SKUs by SALES (the 1688 booked-count demand signal) via pnpm rank-skus
(scripts/rank-skus.ts) so a generation run targets the proven winners instead of every SKU.
Read-only, zero API calls — always safe to run.
Usage
- Rank:
pnpm rank-skus --store <media-dir> --top <N>→ a ranked table (clip-ready gen5 SKUs only by default; add--allto include SKUs with no gen5 set).--storeis required (or setMACRO_PICKLE_STORE_DIR). - Read the elbow: there's usually a clear sales drop-off — recommend the cut to the user (e.g. "top 8 = the Pareto winners") rather than an arbitrary N.
- Hand off to clips:
pnpm rank-skus --store <dir> --top <N> --ids→ CSV of winner SKU ids →pnpm gen-clips --store <dir> --skus <csv>(or run /pickle-clips with that--skus).
Notes
- Demand signal =
manifest.jsonsalesperofferId. Requires the store dir to containmanifest.json+<category>/<sku>/gen5/. --jsonfor machine output;--idsfor the bare CSV (the pipe togen-clips --skus).- This is the front half of the money loop: rank winners → /pickle-clips → cull in edit → post. It does not spend anything; the spend gate lives in /pickle-clips.
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.
- 5d ago First seen · 31 lines · 20 tokens per session scan A e128d4372544
pickle-winners is a command published in the GitHub repository MrJPTech/macro-pickle (2 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 449 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
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.
ebay-orders
Check recent eBay orders and fulfillment status.
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.