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 rules/movictor99/shopify-theme-builder/shopify-theme-buildergit clone --depth 1 https://github.com/moVictor99/shopify-theme-builderWrote 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/rules/movictor99/shopify-theme-builder/shopify-theme-builder)<a href="https://agentmods.dev/rules/movictor99/shopify-theme-builder/shopify-theme-builder"><img src="https://agentmods.dev/badge/rules/movictor99/shopify-theme-builder/shopify-theme-builder.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 | $0.00058 | $0.00389 |
| Opus 5 | $0.00029 | $0.00195 |
| Sonnet 5 | $0.00012 | $0.00078 |
| Haiku 4.5 | $0.00006 | $0.00039 |
Grade A, and why
shopify-theme-builder 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 3d 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 Theme Builder (Cursor rule)
When the task involves building or designing a Shopify theme, follow the workflow in this repo. It is agent-agnostic and self-contained.
- Read
AGENTS.md(orSKILL.md) for the full workflow, phase gates, and the design-token vocabulary. Start there. - Open
references/*.mdonly when the relevant phase needs them (progressive disclosure). Copyassets/theme-skeleton/as the scaffold base and pattern-match every new section againstexamples/section-hero.liquid.
Three hard constraints you must not trade away:
- Shopify-compliant — valid
{% schema %}on every section,theme-checkclean, no deprecated Liquid, mirror Dawn when unsure. - 100% theme-editor controllable — no hard-coded text/color/font/image/ layout; every value is a setting, block, or section group.
- Systemized — one token layer (
settings_schema.json→ CSS custom properties); sections readvar(--token)only.
Phases (gated): 0 discovery interview (blocking) → 1 architecture plan (approval)
→ 2 scaffold → 3 build sections → 4 design pass → 5 i18n & RTL → 6 QA
(shopify theme check + scripts/validate_theme.py + references/qa-checklist.md)
→ 7 package. Do not skip the interview; do not cross a gate early.
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.
- 3d ago First seen · 31 lines · 58 tokens per session scan A fc28f73efdd6
shopify-theme-builder is a cursor rule published in the GitHub repository moVictor99/shopify-theme-builder (4 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 389 once invoked, about $0.0003 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 cursor rules, from other repositories
codemap
Build an explorable isometric diagram of a codebase — blocks on a grid, a component index, a what-it-does/how-it's-built panel, and real data moving along the edges. Use when asked to map, diagram or visually explain how a system fits together.
main
GhostSwap Partners API integration conventions (auth, idempotency, polling, error handling). Apply when working on swap, exchange, quote, or crypto-conversion code.
qapla-api
Integrate with or answer questions about the Qapla' shipping & tracking REST API (public v1.3). Use this when working with Qapla' to push shipments or raw orders, generate and confirm carrier labels, track parcels, get real-time multi-carrier quotes, look up pickup points (PUDO), verify addresses, list couriers and…
project
Glitch Payment Gateway project coding guidelines — WooCommerce payment plugin conventions, stack, folder structure, dev commands.
web
Storefront component rules.
java-springboot-jpa-cursorrules-prompt-file
description: "Cursor rules for Java development with Springboot and JPA integration." globs: / alwaysApply: false.