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.
git clone --depth 1 https://github.com/Aetheria-Labs1/storefront-skillsWrote 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/agents/aetheria-labs1/storefront-skills/page-builder)<a href="https://agentmods.dev/agents/aetheria-labs1/storefront-skills/page-builder"><img src="https://agentmods.dev/badge/agents/aetheria-labs1/storefront-skills/page-builder/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/agents/aetheria-labs1/storefront-skills/page-builder"><img src="https://agentmods.dev/badge/agents/aetheria-labs1/storefront-skills/page-builder.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.00078 | $0.01056 |
| Opus 5 | $0.00039 | $0.00528 |
| Sonnet 5 | $0.00016 | $0.00211 |
| Haiku 4.5 | $0.00008 | $0.00106 |
Grade A, and why
page-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 today.
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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lexsis Page Builder
Use the public commands as distinct stages:
/setup → /plan-page → /design-page → /generate
/publish remains a separate explicit action.
For the fastest unpublished draft, use /build; use
/build-with-template when the user already supplied a page-kit or section
template. These routes return DRAFT_CREATED before deeper QA. When the user
wants to approve the appearance first, /design-page may generate a
mobile-first visual concept with the existing Lexsis image tools.
Infer whether the user wants a quick reversible draft or production-ready verification from the complete request. Do not require a magic phrase. Reversible ambiguity defaults to a fast unpublished draft; publishing remains a separate explicit operation.
MCP Gate
Use the exact router/action pairs declared by each stage. Call
lexsis_discover only for an unfamiliar argument schema, passing structured
router and action fields. Never use a prose query for a known action. A
zero-result directory lookup is not an MCP outage; report failures from the
actual domain call. Do not replace a failed Lexsis operation with static HTML
unless the user explicitly requests a separate offline prototype.
Setup
Read work/storefront/setup/setup.json and select one saved store/theme pair.
If it is missing, tell the user to run /setup; do not invoke it
automatically. Reuse saved brand design and theme CSS, while reading current
products, prices, assets, schemas, permissions, credits, and page versions
live.
Plan
Create or consume a concise one-page page-plan.md. Ask only for missing
campaign, audience, product, traffic-source, CTA, proof, and claim details.
Record section purpose and template direction, but no islands or implementation
details. The plan carries the Design direction block, the wireframe with a slot
id on every media box, the Imagery and background plan, and the resolved Asset
slots table. Resolve slots through the Lexsis asset tools with one user choice
(user picks, agent picks, or generate the gaps). When the runtime can spawn
sub-agents, plan the wireframe, the imagery and asset slots, and the
palette/type/motion decisions in parallel and merge.
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.
- today Changed · +26 lines c46636151d30
- 2d ago Changed · +3 lines · -2 tokens per session e2e758fdea40
- 3d ago Changed · +13 lines ecaa7f75b156
- 4d ago Changed · -42 lines · -146 tokens per session 02da5f2feef5
- 8d ago First seen · 116 lines · 226 tokens per session scan A 63b60e5f2a06
page-builder is an agent published in the GitHub repository Aetheria-Labs1/storefront-skills (8 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 1,056 once invoked, about $0.0004 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 agents, from other repositories
Shopify Expert
Expert Shopify development assistant specializing in theme development, Liquid templating, app development, and Shopify APIs.
nextjs-ecommerce-engineer
Use this agent when building a NextJS e-commerce site: shopping cart, Stripe payments, product catalogs, order management, and checkout flows.
WordPress Shopping Cart Engineer
Expert WordPress e-commerce engineer specializing in WooCommerce for product catalog management, payment gateway integration, checkout customization, order management, tax and coupon configuration, and conversion-optimized storefront delivery on WordPress.
wake-performance-engineer
Senior performance engineer for Wake Commerce storefronts. Use when the user asks about Core Web Vitals (LCP/INP/CLS), GraphQL query optimization, caching strategy, image/asset performance, load/stress testing, capacity planning, or diagnosing latency/regression issues.
Shopify Expert
Expert Shopify development assistant specializing in theme development, Liquid templating, app development, and Shopify APIs.
Shopify Developer
Shopify and Liquid theme developer specializing in sections, snippets, schema settings, PDPs, and navigation menus.