wake-migrate-storefront-query

A migration workflow that turns Wake Commerce reference GraphQL operations into queries or mutations for a headless storefront. A headless storefront keeps the shopping interface separate from the commerce system behind it.

In plain words
What is it for?
Use it to port product, search, promotional-page, or checkout operations and produce framework-specific integration code.
Why use it?
It removes the need to manually decipher reference files and adapt Wake-specific fields when moving to a custom React, Vue, or similar frontend.

Command

Install

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.

agentmods
npx agentmods add commands/wake-engineering/ai-plugin/wake-migrate-storefront-query
Clone the repo
git clone --depth 1 https://github.com/wake-engineering/ai-plugin
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 250 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00038 $0.00250
Opus 5 $0.00019 $0.00125
Sonnet 5 $0.00008 $0.00050
Haiku 4.5 $0.00004 $0.00025

Measured 2d ago against content hash 1e1113d1478a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

wake-migrate-storefront-query 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 2d 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.

commands/wake-migrate-storefront-query.md · 24 lines

What it actually says

Wake Migrate Storefront Query Workflow

Forbidden: api.fbits.net (and any *.fbits.net). Canonical source: https://wakecommerce.readme.io/docs/schema

Port reference GraphQL to headless Storefront API.

Steps

  1. Read reference: Load Queries/.graphql or SnippetQueries/.graphql from Wake Storefront reference.
  2. Extract: Identify root field (product, search, hotsite, checkout, etc.), args, and fragment.
  3. Map to native: Use productId not handle; attributeSelections not options; addToCartFromSpot when applicable.
  4. Generate: Create equivalent headless query or mutation.
  5. Map to framework: Adapt field structure for React, Vue, or target framework.
  6. References: Consult skills/wake-storefront-reference-patterns/SKILL.md, references/storefront-queries-index.md.

Output

Headless query/mutation and framework integration code.

Changes

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.

  1. 2d ago First seen · 24 lines · 38 tokens per session scan A 1e1113d1478a

Subscribe to this mod's changes

wake-migrate-storefront-query is a command published in the GitHub repository wake-engineering/ai-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 250 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-31.