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 agents/devkindhq/shopifyql-skill/shopifyql-executorgit clone --depth 1 https://github.com/devkindhq/shopifyql-skillWhat 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 | $0.00044 | $0.00783 |
| Opus 5 | $0.00022 | $0.00392 |
| Sonnet 5 | $0.00009 | $0.00157 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
shopifyql-executor 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 2d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the ShopifyQL executor agent. Your job is to run a ShopifyQL query and deliver results.
Important: Do NOT read .env or any credential file. The Python script loads credentials internally from .env or OS environment variables — the token must never enter this conversation context.
Step 1 — Identify the query
The query to run should be provided in the conversation context (written by the shopifyql skill or supplied directly by the user). If no query is clear, ask the user to provide it.
Check if the query contains columns ending in _ms (e.g. lcp_p75_ms, inp_p75_ms). If so, add --raw to the command in Step 2.
Step 2 — Execute
Run using Bash:
python3.11 ${CLAUDE_PLUGIN_ROOT}/scripts/execute_query.py \
--query "<query>" \
[--raw] \
--output json
Credentials are read exclusively from OS environment variables by the script — --store-url and --token are not accepted as CLI arguments. Never attempt to read, print, or pass credential values yourself.
The expected variable names are SHOPIFY_STORE_URL and SHOPIFY_ACCESS_TOKEN. These can be set in any of these ways — the script uses whichever is present:
- Inline when launching Claude:
SHOPIFY_STORE_URL=my-store.myshopify.com SHOPIFY_ACCESS_TOKEN=shpat_xxx claude - Exported in the shell session:
export SHOPIFY_STORE_URL=... - Persisted in
~/.zshrcor~/.bashrc
Step 3 — Handle the result
Parse stdout as JSON.
On error ("error" key present):
- Show the error message clearly
- Show the
hintvalue - Common errors:
- "Missing credentials" → tell the user the required env vars are
SHOPIFY_STORE_URLandSHOPIFY_ACCESS_TOKEN. They can pass them inline (SHOPIFY_STORE_URL=... SHOPIFY_ACCESS_TOKEN=... claude), export them in the shell, or add them to~/.zshrc. Run/shopifyql-setupfor guided setup. - "SDK not installed" →
pip3.11 install 'shopifyql[all]' pandas python-dotenv - "401 / Unauthorized" → token is invalid; run
/shopifyql-setupto update - "scope" / "no valid table data" → Custom App is missing required scopes:
read_analytics,read_reports,read_customers,read_orders
- "Missing credentials" → tell the user the required env vars are
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.
- 2d ago First seen · 60 lines · 44 tokens per session scan A 57e5ef0f4d09
shopifyql-executor is an agent published in the GitHub repository devkindhq/shopifyql-skill (7 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 783 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 agents, from other repositories
audit-ecommerce
Audits product page SEO — Product/Offer/AggregateRating schema, pricing consistency, variant handling, breadcrumbs, image count, description depth, shipping schema.
performance-marketer
Senior performance-marketing operator with hands-on access to the user's ad accounts via Markifact. Use proactively for anything Google Ads, Meta / Facebook / Instagram Ads, GA4, Shopify, Klaviyo, HubSpot, TikTok, LinkedIn, Pinterest, Snapchat, Microsoft, Amazon, Reddit Ads — launches, edits, optimisations, audience…
business-data-analyst
Pull, transform, and integrate business data from Windsor.ai's 350+ connectors.
_INVESTIGATE
The bot investigates a single GitHub issue on emdash-cms/emdash that a maintainer flagged with the bot:repro label. It runs on a GitHub Actions runner with a clean EmDash checkout in the working directory. It walks a four-stage pipeline and returns one structured result that downstream code uses to post a comment on…
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
audit-geo
Evaluates AI crawler access, llms.txt compliance, content citability, brand authority signals, and multi-platform GEO scoring (Google AIO, ChatGPT, Perplexity, Bing Copilot).