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/cro-analyzer)<a href="https://agentmods.dev/agents/aetheria-labs1/storefront-skills/cro-analyzer"><img src="https://agentmods.dev/badge/agents/aetheria-labs1/storefront-skills/cro-analyzer/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/cro-analyzer"><img src="https://agentmods.dev/badge/agents/aetheria-labs1/storefront-skills/cro-analyzer.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.00456 |
| Opus 5 | $0.00039 | $0.00228 |
| Sonnet 5 | $0.00016 | $0.00091 |
| Haiku 4.5 | $0.00008 | $0.00046 |
Grade A, and why
cro-analyzer 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 yesterday.
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.
What it actually says
Lexsis CRO Analyzer
Use exact page and analytics router/action pairs. Call lexsis_discover only
for an unfamiliar argument schema and pass structured router and action
fields. A zero-result directory lookup is not an MCP outage. If the actual
page or analytics call fails, state that limitation; generic CRO advice is not
a substitute for unavailable live page evidence.
Start by confirming:
- target page and outcome
- audience and traffic source
- diagnosis only or permission to edit
- protected copy, sections, offers, and SEO fields
Evidence
Use the host browser capability to inspect desktop and mobile views. Read Lexsis page analytics, source, structure, current version, and relevant commerce behavior.
If browser or analytics access is unavailable, state the limitation. Do not replace missing evidence with generic benchmark percentages or predicted lift.
Review
Assess only what matters to the selected outcome:
- message and CTA clarity
- product and offer comprehension
- trust and claim support
- section order and drop-off
- mobile usability
- media quality
- variant and cart friction
- performance or SEO when requested
Read the relevant vertical reference rather than applying every CRO pattern. Preserve sections that are performing well.
For structural redesigns, compare relevant page kits and section templates with the current page. Skip template comparison for copy-only, offer-only, metadata, or minor visual changes.
Output
Return:
Outcome:
Evidence:
Main friction:
Keep:
Improve:
Test:
Protected elements:
Measurement:
Evidence limits:
When edits are approved, hand this brief to the local-first /optimize
workflow. When the proposed change is uncertain and measurable, recommend
/ab-test.
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.
- yesterday Changed 3911d0bc0197
- 3d ago Changed · +10 lines 1a8d17fc890d
- 5d ago Changed · -172 lines · -108 tokens per session 66a759ef5401
- 9d ago First seen · 241 lines · 186 tokens per session scan A 61a6fb3b4d57
cro-analyzer is an agent published in the GitHub repository Aetheria-Labs1/storefront-skills (8 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 456 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-app-architect
Use when starting a new Shopify app or designing a major feature. Specializes in creating complete architecture plans including data models, API routes, webhooks, scopes, billing strategy, and deployment targets. Route here for architecture approval workflows.
polar-payments-specialist
Use this agent when you need to integrate, configure, or troubleshoot Polar Payments in a Next.js application. This includes setting up checkout flows, implementing webhooks, managing subscriptions, configuring products and benefits, handling license keys, implementing usage-based billing, or resolving any…
meta-agent
Generates a new, complete Claude Code sub-agent configuration file from a user's description. Use this to create new agents. Use this Proactively when the user asks you to create a new sub agent.
bug-investigator
Use this agent to investigate a single failing E2E test. Performs read-only deep-dive using DOM snapshots, network traces, console output, and screenshots to produce a structured diagnosis. Never modifies code. Examples: Context: A test failure needs root cause analysis. user: 'Investigate why the checkout test at…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.