wake-product-page

wake-product-page is a command for coding agents from wake-engineering/ai-plugin. It costs 43 tokens per session (275 once invoked), scanned A, original, MIT.

A workflow for building a Wake Commerce product detail page—the page where shoppers view one product, choose a variant, see prices and images, and add it to a cart.

In plain words
What is it for?
Use it to generate a product-page component or implementation with the product query, variant selection, price and image display, and add-to-cart behavior.
Why use it?
It provides the Wake-specific steps for resolving variants and sending the right product information when shoppers add customized or subscription products.

Command

Part of the wake-storefront plugin — 8 skills, 10 commands, 8 agents, 1 MCP server shipped together

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-product-page
Clone the repo
git clone --depth 1 https://github.com/wake-engineering/ai-plugin

Or install wake-storefront, the plugin that ships this one along with the rest of its 8 skills, 10 commands, 8 agents, 1 MCP server.

Wrote 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.

agentmods badge for wake-product-page

README.md
[![agentmods](https://agentmods.dev/badge/commands/wake-engineering/ai-plugin/wake-product-page.svg)](https://agentmods.dev/commands/wake-engineering/ai-plugin/wake-product-page)
Your own site
<a href="https://agentmods.dev/commands/wake-engineering/ai-plugin/wake-product-page"><img src="https://agentmods.dev/badge/commands/wake-engineering/ai-plugin/wake-product-page.svg" alt="Measured on agentmods" height="20"></a>
Per session 43 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 275 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.00043 $0.00275
Opus 5 $0.00022 $0.00138
Sonnet 5 $0.00009 $0.00055
Haiku 4.5 $0.00004 $0.00028

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

Security

Grade A, and why

wake-product-page 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 4d 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-product-page.md · 23 lines

What it actually says

Wake Product Page Workflow

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

Build a product detail page for Wake Commerce headless storefront.

Steps

  1. Load product: Call product(productId, partnerAccessToken) with attributeSelections(selected: $selections) when product has variants.
  2. Resolve variant: Use selectedVariant when selections match; use root productVariantId for single-variant.
  3. Render: Prices (listPrice, price, discountPercentage), images (with dimensions), add-to-cart button.
  4. Add-to-cart: Use productVariantId from selectedVariant or root; include selections when variants; include customizations and subscriptionGroups when required.
  5. References: Consult skills/wake-product-variants/SKILL.md, skills/wake-storefront-api/references/products.md.

Output

Product page component or implementation with GraphQL query, variant resolution, and add-to-cart flow.

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. 4d ago First seen · 23 lines · 43 tokens per session scan A bc0c0f6875b2

Subscribe to this mod's changes

wake-product-page is a command published in the GitHub repository wake-engineering/ai-plugin (2 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 275 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.