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 skills add TeamDijon/shopify-rules --skill research-shopify-rulegit clone --depth 1 https://github.com/TeamDijon/shopify-rulesWrote 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/skills/teamdijon/shopify-rules/research-shopify-rule)<a href="https://agentmods.dev/skills/teamdijon/shopify-rules/research-shopify-rule"><img src="https://agentmods.dev/badge/skills/teamdijon/shopify-rules/research-shopify-rule/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/skills/teamdijon/shopify-rules/research-shopify-rule"><img src="https://agentmods.dev/badge/skills/teamdijon/shopify-rules/research-shopify-rule.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.00049 | $0.01412 |
| Opus 5 | $0.00024 | $0.00706 |
| Sonnet 5 | $0.00010 | $0.00282 |
| Haiku 4.5 | $0.00005 | $0.00141 |
Grade A, and why
research-shopify-rule 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 9d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research and create a Shopify theme development rule
You are researching Shopify Liquid patterns to produce a well-documented rule for AI consumption. The topic is: $ARGUMENTS
Read the reference files in this skill's directory before starting:
- references/existing-coverage.md -- what Shopify's cursor rules already cover (avoid duplicating)
- references/theme-guide.md -- recommended themes and how to search them
- references/rule-template.md -- the format every rule must follow
Phase 1 -- Scope
- Identify the core topic from
$ARGUMENTS. Break it down: what Liquid objects, filters, tags, or Shopify features are involved? - Check for overlap using the three-level approach:
- Read
references/existing-coverage.mdfor a summary of what Horizon's cursor rules cover. If the topic overlaps, note what the existing rules cover and focus on what they do NOT cover (advanced patterns, workarounds, edge cases). - Check
rules/INDEX.mdfor rules already written in this repo. - If
shopify-themes/horizon/is present, scan its.cursor/rules/directory for the latest coverage. This takes priority over the static summary inexisting-coverage.md.
- Read
- Search
rules/for existing rules on the topic. If a related rule exists, determine whether to extend it or create a new one. - Present your scope assessment to the user before proceeding.
Phase 2 -- Research
Search for patterns across the themes in shopify-themes/. Use Explore agents to parallelize the search.
If shopify-themes/ is empty or has few themes, expand web research. The skill can still produce valuable rules from Shopify documentation alone, though cross-theme comparisons will be limited. Suggest the user adds themes for richer research -- see references/theme-guide.md for recommendations.
What to search for
- Snippet files related to the topic (search by filename and content in
snippets/folders) - Section files that implement related functionality (in
sections/folders) - Liquid patterns using relevant filters, tags, and objects
- Comments mentioning workarounds, tricks, or explanations (search for terms like "workaround", "hack", "trick", "note:", "important:", "TODO")
- Schema patterns in section
{% schema %}blocks that relate to the topic
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 122 lines · 49 tokens per session scan A 376f7248f254
research-shopify-rule is a skill published in the GitHub repository TeamDijon/shopify-rules (12 stars, last pushed 7mo ago), licensed MIT. It adds 49 tokens to every session and 1,412 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-30.
Other skills, from other repositories
amazon-reviews-api-skill
This skill helps users automatically extract Amazon product reviews via the Amazon Reviews API. Agent should proactively apply this skill when users express needs like getting reviews for Amazon product with ASIN B07TS6R1SF, analyzing customer feedback for a specific Amazon item, getting ratings and comments for a…
amazon-competitor-analyzer
Scrapes Amazon product data from ASINs using browseract.com automation API and performs surgical competitive analysis. Compares specifications, pricing, review quality, and visual strategies to identify competitor moats and vulnerabilities.
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.
food-order
Reorder previous Foodora orders, preview cart contents, and track delivery ETA/status with ordercli. Use when the user wants to reorder food, check delivery status, or browse recent Foodora order history. Never confirm an order without explicit user approval.
product-description-generator
E-commerce product description generator for any platform. Generates optimized titles, bullet points, descriptions, and backend keywords using competitor research + keyword scoring + FABE copywriting. Two modes: (A) Create — generate listing from product specs with optional competitor analysis, (B) Optimize — improve…
amazon-price-tracker
Amazon price monitoring and competitive pricing intelligence. Real-time price tracking, Buy Box analysis, promotion detection, and dynamic pricing strategy optimization. Use when the user asks about price monitoring, competitor pricing, Buy Box tracking, or pricing strategy.