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 skills/wake-engineering/ai-plugin/wake-storefront-apinpx skills add wake-engineering/ai-plugin --skill wake-storefront-apigit clone --depth 1 https://github.com/wake-engineering/ai-pluginWhat 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.00706 |
| Opus 5 | $0.00029 | $0.00353 |
| Sonnet 5 | $0.00012 | $0.00141 |
| Haiku 4.5 | $0.00006 | $0.00071 |
Grade A, and why
wake-storefront-api 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wake Storefront API
Forbidden: api.fbits.net (and any *.fbits.net). Canonical source: https://wakecommerce.readme.io/docs/schema
GraphQL-based Storefront API for Wake Commerce headless storefronts. Covers products, search, checkout, cart, and customer operations.
When to Use
- Building product listing, detail, or search pages
- Implementing checkout or cart flows
- Integrating customer account features
- Writing GraphQL queries for Wake Commerce
- Migrating or extending Wakelabs storefront patterns
API Overview
The Storefront API is GraphQL. Base URL and auth depend on partner configuration. Key operations:
| Operation | Root Field | Use Case |
|---|---|---|
| Product | product(productId, partnerAccessToken) |
Product detail, variants, prices |
| Search | search(query, partnerAccessToken) |
Product search, filters, pagination |
| Checkout | checkout(checkoutId) |
Cart contents, shipping, totals |
| Cart | See references/checkout-cart.md | Mini cart, add to cart |
Core Principles
- Use
partnerAccessTokenwhen querying in partner/wholesale context. - Avoid N+1: Batch related data in a single query; use fragments for reuse.
- Select only needed fields: Do not over-fetch; GraphQL allows precise selection.
- Handle
@include(if:)for conditional checkout data whenhasCheckoutis false.
Product Queries
See references/products.md for:
- Product detail with variants and attribute selections
SingleProductDatafragment usage- Price fields (listPrice, price, discountPercentage, installmentPlans)
- Image URLs with dimensions
Search Queries
- Root:
search(query, partnerAccessToken) - Use
productsByOffsetfor paginated results (limit, offset, sortKey, sortDirection, filters) - Aggregations: filters, priceRanges, minimumPrice, maximumPrice
- Items: productId, productName, alias, images, prices, promotions, addToCartFromSpot
Checkout & Cart
See references/checkout-cart.md for:
- Checkout query structure
- Products in checkout (listPrice, price, quantity, customization)
- shippingFee, subtotal, total
- Mini cart and add-to-cart patterns
What ships with it
3 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.
- 2d ago First seen · 77 lines · 58 tokens per session scan A 8bca368dc825
wake-storefront-api is a skill published in the GitHub repository wake-engineering/ai-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 706 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 skills, from other repositories
cloudflare-registrar
Cloudflare Registrar: domain availability, prices, registration via mcporter.
amazon-bestseller-listing
Amazon Best Sellers listing scraper: extract product cards from any Amazon Best Sellers (zgbs) or /gp/bestsellers/ category page — returns rank (position on chart), asin, title, url, image, imageAlt, price, stars, reviewCount, ratingRaw per item, plus category metadata (categoryName, categoryFullName, categoryUrl) and…
amazon-reviews-api-skill
This skill helps users automatically extract Amazon product reviews via the Amazon Reviews API. Agent should proactively apply this skill when users express needs like getting reviews for Amazon product with ASIN B07TS6R1SF, analyzing customer feedback for a specific Amazon item, getting ratings and comments for a…
amazon-competitor-analyzer
Scrapes Amazon product data from ASINs using browseract.com automation API and performs surgical competitive analysis. Compares specifications, pricing, review quality, and visual strategies to identify competitor moats and vulnerabilities.
weekly-report
Structure and data sources for the weekly inventory report. Load this when the task is "weekly report", "Monday report", or "summarize inventory status".
shopify-hydrogen
Hydrogen storefront implementation cookbooks. Some of the available recipes are: B2B Commerce, Bundles, Combined Listings, Custom Cart Method, Dynamic Content with Metaobjects, Express Server, Google Tag Manager Integration, Infinite Scroll, Legacy Customer Account Flow, Markets, Partytown + Google Tag Manager…