Borrowing it
Nothing to install: this file belongs to TeamDijon/shopify-rules. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TeamDijon/shopify-rules/main/CLAUDE.mdgit 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/instructions/teamdijon/shopify-rules/claude-md)<a href="https://agentmods.dev/instructions/teamdijon/shopify-rules/claude-md"><img src="https://agentmods.dev/badge/instructions/teamdijon/shopify-rules/claude-md/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/instructions/teamdijon/shopify-rules/claude-md"><img src="https://agentmods.dev/badge/instructions/teamdijon/shopify-rules/claude-md.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.00346 | $0.00346 |
| Opus 5.5 | $0.00138 | $0.00138 |
| Sonnet 5.5 | $0.00069 | $0.00069 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
shopify-rules CLAUDE.md 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.
What it actually says
shopify-rules
A collection of AI-consumable rules for Shopify Liquid theme development, plus skills to create more.
Project structure
rules/INDEX.md-- master index of all rulesrules/BACKLOG.md-- pending topics discovered but not yet written as rulesrules/<category>/-- rule files organized by category (folders created as needed)shopify-themes/-- optional user-supplied Shopify themes for research (gitignored)
Available skills
/discover-rule-topics <optional focus>-- mine themes for patterns, enrich the backlog/research-shopify-rule <topic>-- deep cross-theme research, produce a thorough rule (5 phases)/quick-rule <topic>-- fast rule creation from official docs (3 phases)
Overlap detection
Before creating a rule, check for overlap at three levels:
existing-coverage.md(in skill references) -- static summary of Horizon's 43 cursor rulesrules/INDEX.md-- rules already written in this reposhopify-themes/horizon/.cursor/rules/-- live scan if Horizon theme is present
Guidelines
- Rules are standalone markdown files. Do not reference project-specific paths within rule content.
- Never invent Liquid filters, tags, or objects. Only use what exists in Shopify's Liquid implementation.
- Use
{% liquid %}blocks for multiline logic in code examples. - Create category folders on-the-fly as needed when writing rules.
- Source references use relative theme paths (e.g.,
dawn/snippets/price.liquid) or Shopify doc URLs.
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 · 33 lines · 346 tokens per session scan A d5838b27e83a
shopify-rules CLAUDE.md is an instructions file published in the GitHub repository TeamDijon/shopify-rules (12 stars, last pushed 8mo ago), licensed MIT. It adds 346 tokens to every session, about $0.0014 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 instructions, from other repositories
vibetags com-example-service-OrderService.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for orderservice, rules for method calculatetax, rules for method processpayment, rules for method validateorder and context & focus.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.