Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/eric861129/SKILLS_All-in-onenpx agentmods add skills/eric861129/skills_all-in-one/shopify-expertWrote 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/eric861129/skills_all-in-one/shopify-expert)<a href="https://agentmods.dev/skills/eric861129/skills_all-in-one/shopify-expert"><img src="https://agentmods.dev/badge/skills/eric861129/skills_all-in-one/shopify-expert/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/eric861129/skills_all-in-one/shopify-expert"><img src="https://agentmods.dev/badge/skills/eric861129/skills_all-in-one/shopify-expert.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.00117 | $0.01524 |
| Opus 5 | $0.00059 | $0.00762 |
| Sonnet 5 | $0.00023 | $0.00305 |
| Haiku 4.5 | $0.00012 | $0.00152 |
Grade A, and why
shopify-expert 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 8d 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.
This is a copy
94% identical to shopify-expert — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shopify Expert
Senior Shopify developer with expertise in theme development, headless commerce, app architecture, and custom checkout solutions.
Core Workflow
- Requirements analysis — Identify if theme, app, or headless approach fits needs
- Architecture setup — Scaffold with
shopify theme initorshopify app create; configureshopify.app.tomland theme schema - Implementation — Build Liquid templates, write GraphQL queries, or develop app features (see examples below)
- Validation — Run
shopify theme checkfor Liquid linting; if errors are found, fix them and re-run before proceeding. Runshopify app devto verify app locally; test checkout extensions in sandbox. If validation fails at any step, resolve all reported issues before moving to deployment - Deploy and monitor —
shopify theme pushfor themes;shopify app deployfor apps; watch Shopify error logs and performance metrics post-deploy
Reference Guide
Load detailed guidance based on context:
| Topic | Reference | Load When |
|---|---|---|
| Liquid Templating | references/liquid-templating.md |
Theme development, template customization |
| Storefront API | references/storefront-api.md |
Headless commerce, Hydrogen, custom frontends |
| App Development | references/app-development.md |
Building Shopify apps, OAuth, webhooks |
| Checkout Extensions | references/checkout-customization.md |
Checkout UI extensions, Shopify Functions |
| Performance | references/performance-optimization.md |
Theme speed, asset optimization, caching |
Code Examples
Liquid — Product template with metafield access
{% comment %} templates/product.liquid {% endcomment %}
<h1>{{ product.title }}</h1>
<p>{{ product.metafields.custom.care_instructions.value }}</p>
{% for variant in product.variants %}
<option
value="{{ variant.id }}"
{% unless variant.available %}disabled{% endunless %}
>
{{ variant.title }} — {{ variant.price | money }}
</option>
{% endfor %}
{{ product.description | metafield_tag }}
What ships with it
5 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.
- 8d ago First seen · 185 lines · 117 tokens per session scan A 0638b4839c1c
shopify-expert is a skill published in the GitHub repository eric861129/SKILLS_All-in-one (52 stars, last pushed 4mo ago), licensed MIT. It adds 117 tokens to every session and 1,524 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to shopify-expert, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
frontend
Use when building React components, optimizing performance, analyzing bundle sizes, scaffolding projects, implementing accessibility, reviewing frontend code quality, performing visual overhauls, or designing UI/UX systems.
design-agent
You are the Design agent for this project. You own React components, page routes, design tokens, and visual layout.
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance…
remotion-best-practices
Best practices for Remotion - Video creation in React.
comp-gen
Generate React/Vue/Svelte components.
blog
Generate blog engine with MDX support.