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 quick-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/quick-rule)<a href="https://agentmods.dev/skills/teamdijon/shopify-rules/quick-rule"><img src="https://agentmods.dev/badge/skills/teamdijon/shopify-rules/quick-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/quick-rule"><img src="https://agentmods.dev/badge/skills/teamdijon/shopify-rules/quick-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.00056 | $0.01723 |
| Opus 5.5 | $0.00022 | $0.00689 |
| Sonnet 5.5 | $0.00011 | $0.00345 |
| Haiku 4.5 | $0.00006 | $0.00172 |
Grade A, and why
quick-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 1mo 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick rule -- write a rule from known patterns
You are writing a Shopify Liquid rule for a well-documented topic. This skill is the fast path: lean on Shopify's official documentation and your own knowledge rather than mining local themes.
The topic is: $ARGUMENTS
Read the reference files in this skill's directory before starting:
- references/rule-template.md -- the format every rule must follow
- references/existing-coverage.md -- what Shopify's cursor rules already cover (avoid duplicating)
When to use this skill vs /research-shopify-rule
Use /quick-rule when |
Use /research-shopify-rule when |
|---|---|
| The pattern is well-documented on shopify.dev | The pattern has little or no official documentation |
| Shopify Liquid docs fully describe the objects and filters involved | The topic involves undocumented workarounds or community-discovered tricks |
| The topic is a single, focused technique | The topic spans multiple interacting patterns |
| Examples from official docs are sufficient | You need cross-theme comparison to find the best approach |
| Complexity is basic or intermediate | Complexity is advanced (nested loops, recursive-like patterns) |
If you discover during Phase 1 that the topic is more complex than expected, stop and suggest switching to /research-shopify-rule before investing time in a draft.
Phase 1 -- Scope
1.1 Parse the topic
Break down $ARGUMENTS:
- What Liquid objects, filters, tags, or Shopify features are involved?
- Is this a single technique or does it combine multiple concepts?
- What complexity level does this feel like: basic, intermediate, or advanced?
1.2 Check for overlap
Use the three-level overlap check:
- Read
references/existing-coverage.md-- does this overlap with Horizon's cursor rules? If so, note what the existing rules cover and focus on what they do NOT cover. - Check
rules/INDEX.mdfor existing rules on the topic. If a related rule exists, determine whether to extend it or create a new one. - If
shopify-themes/horizon/is present, scan its.cursor/rules/for the latest coverage. This takes priority over the static summary.
What ships with it
2 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.
- 1mo ago First seen · 186 lines · 56 tokens per session scan A 037646da50ef
quick-rule is a skill published in the GitHub repository TeamDijon/shopify-rules (12 stars, last pushed 8mo ago), licensed MIT. It adds 56 tokens to every session and 1,723 once invoked, about $0.0002 per session on Opus 5.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
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 Photoshoot Workflow
A workflow for turning one product photo into a set of four e-commerce images from different visual directions.
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.
cloudbase-wechat-integration
A guide for connecting CloudBase applications to WeChat services, including payments, official accounts, and user identity.