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 skills add Aetheria-Labs1/storefront-skills --skill optimizegit 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/skills/aetheria-labs1/storefront-skills/optimize)<a href="https://agentmods.dev/skills/aetheria-labs1/storefront-skills/optimize"><img src="https://agentmods.dev/badge/skills/aetheria-labs1/storefront-skills/optimize.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.00776 |
| Opus 5 | $0.00016 | $0.00388 |
| Sonnet 5 | $0.00006 | $0.00155 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
optimize 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Optimize a Page
Read:
references/evidence-led-cro.md
Use the needed exact actions from
lexsis_pages.edit_context, lexsis_pages.source,
lexsis_pages.section_source, lexsis_pages.compile,
lexsis_pages.integrity, lexsis_pages.diff, lexsis_analytics.page,
lexsis_analytics.timeseries, lexsis_analytics.attribution,
lexsis_template_library.search_page_kits,
lexsis_template_library.search_sections,
lexsis_drafts.page_update_section, and lexsis_drafts.page_patch. Resolve
only unfamiliar schemas through exact router/action discovery. A zero-result
directory lookup does not make page or analytics data unavailable. If the
actual live read fails, state that limitation; generic CRO guidance is not a
substitute.
The full skill pack includes optional deeper design guidance at
references/lexsis-design-capabilities.md. Every edit obeys
the house rules in references/design-rules.md; an
optimization never adds emoji, gradients, hover transforms, or a section
background.
Start by confirming:
- Target outcome: conversion, add-to-cart, AOV, bounce, trust, mobile UX, speed, or SEO.
- Target page, audience, and traffic source.
- Diagnosis only or permission to edit.
- Copy, sections, SEO fields, or offers that must remain unchanged.
Do not edit until the objective and scope are clear.
Confirm the page's store/theme binding exists in
work/storefront/setup/setup.json. If it is missing, stop with
Run /setup for this store and theme first. Never run setup automatically.
Use Relevant Guidance Only
Read only the matching section of references/industry-cro.md.
Use general guidance when no industry fits. Treat analytics and observed user behavior as stronger evidence than generic patterns.
Diagnose
- Locate the page and read its analytics, structure, source, and current remote version.
- Open its local page workspace. If missing, adopt the remote source into the standard local files before editing.
- Compare the remote version with the manifest and stop on unexpected drift.
- For a structural redesign, search relevant page kits and sections and compare them with the current structure. Do not force template comparison for copy-only, offer-only, metadata, or minor visual changes.
- Classify proposed changes as keep, improve, replace, remove, or test.
- Present an optimization brief:
What ships with it
9 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.
- agents/openai.yaml 404 B
- references/design-rules.md 17 KB
- references/evidence-led-cro.md 1.2 KB
- references/generate-pdp.md 5.7 KB
- references/generation-protocol.md 12 KB
- references/industry-cro.md 1.7 KB
- references/lexsis-design-capabilities.md 6.4 KB
- references/source-artifact-workflow.md 3.9 KB
- references/source-format.md 8.3 KB
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 1b588de2686f
- yesterday Changed · +3 lines 80c303e2fe8b
- 2d ago Changed · +25 lines 99465f473cb0
- 3d ago Changed · -143 lines · -2 tokens per session b3f7edddd272
- 8d ago First seen · 215 lines · 34 tokens per session scan A aa071295f9b8
optimize is a skill published in the GitHub repository Aetheria-Labs1/storefront-skills (8 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 776 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.
Other skills, from other repositories
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.
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.
food-order
Reorder previous Foodora orders, preview cart contents, and track delivery ETA/status with ordercli. Use when the user wants to reorder food, check delivery status, or browse recent Foodora order history. Never confirm an order without explicit user approval.
product-description-generator
E-commerce product description generator for any platform. Generates optimized titles, bullet points, descriptions, and backend keywords using competitor research + keyword scoring + FABE copywriting. Two modes: (A) Create — generate listing from product specs with optional competitor analysis, (B) Optimize — improve…
amazon-price-tracker
Amazon price monitoring and competitive pricing intelligence. Real-time price tracking, Buy Box analysis, promotion detection, and dynamic pricing strategy optimization. Use when the user asks about price monitoring, competitor pricing, Buy Box tracking, or pricing strategy.