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/shapediver/AppBuilderSdkWrote 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/rules/shapediver/appbuildersdk/ecommerce-tools-api)<a href="https://agentmods.dev/rules/shapediver/appbuildersdk/ecommerce-tools-api"><img src="https://agentmods.dev/badge/rules/shapediver/appbuildersdk/ecommerce-tools-api/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/rules/shapediver/appbuildersdk/ecommerce-tools-api"><img src="https://agentmods.dev/badge/rules/shapediver/appbuildersdk/ecommerce-tools-api.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.00000 | $0.00823 |
| Opus 5.5 | $0.00000 | $0.00329 |
| Sonnet 5.5 | $0.00000 | $0.00165 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
ecommerce-tools-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 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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E-commerce connector and tools API
Keep two typed CrossWindow facades. They share action cores. They do not share one RPC.
Playwright parent/iframe setup is in .cursor/rules/e2e-playwright.mdc. Action-core behavior is in .cursor/rules/appbuilder-actions.mdc.
Schemas
- Canonical action-prop Zod is
features/appbuilder/config/appbuilderActionsTypecheck.ts(UI-free). It includes parameter-source schemas becausesetParameterValue.sourceand model-state sources share createModelState props. - Settings JSON (
appbuildertypecheck.ts) and the e-commerce client (ecommerceapitypecheck.ts) import that file. - Do not import
appbuildertypecheck.tsfrom the e-commerce client. That module pulls Mantine theme and widget validation. features/agent-tools/configmust not import@mantine/or@shapediver/.IAgentThemeisMantineThemeOverrideProps, the JSON theme mirror.getThemestill sends the published theme; functions are already stripped before it is stored.IAddItemToCartDatais the cart-plugin payload, not addToCart action props.- The screenshot tool schema is stricter than
viewportScreenshotPropsSchema. Output isimage_url. Input iscontentType,quality, andresolution. getOutputandgetMetricsharegetOutputContent. Metric mapscontenttovalue.
Runtime
- Do not put live APIs on
window(__appBuilderECommerceConnector,__appBuilderToolsApi). createECommerceApiConnectorActionsis Zustand-only (no hooks, no agent-tools import).useECommerceApiConnectorActionspassescomponentContext.actionsso host camera and other host keys go throughfindAppBuilderActionRegistration.- Tools handshake only when an agent window is set. A Shopify iframe must not always use
window.parent; that spams Tools. - Do not add product query params or window hooks for tests.
- Deployed
appbuilder.shapediver.comsendsCross-Origin-Opener-Policy: same-origin, so a top-level page cannot handshake a localhost popup (window.openeris null).
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 · +1 lines 2225c993642f
- 2d ago First seen · 45 lines · 0 tokens per session scan A 8f4675641682
ecommerce-tools-api is a cursor rule published in the GitHub repository shapediver/AppBuilderSdk (15 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 823 tokens. 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-10-15.
Other cursor rules, from other repositories
vtex-io-vtex-io-admin-react
Apply when building VTEX IO admin-facing React interfaces under the admin builder. Covers VTEX Styleguide and Shoreline usage, admin page composition, data-heavy admin interactions, and keeping administrative interfaces consistent with the VTEX Admin environment. Use for settings pages, moderation tools, dashboards…
vtex-io-vtex-io-storefront-react
Apply when building VTEX IO storefront components under react/ for Store Framework experiences. Covers storefront component structure, css-handles, storefront context hooks, browser-safe data fetching, and how components should behave when used as theme blocks. Use for custom storefront UI, product widgets, banners…
medusa-cursorrules
Cursor rule "medusa-cursorrules" from XD3an/awesome-ai-coding-all-in-one, covering medusa rules, general rules, workflow rules, data model rules and service rules.
faststore-all
Composite skill for the faststore track. Core coding rules and workflow for developing VTEX FastStore storefronts. Use when starting any FastStore development task, writing TypeScript/React components, creating section overrides, extending the BFF, or styling. Covers all primary conventions, safety rules, and the…
faststore-faststore-storefront
Core coding rules and workflow for developing VTEX FastStore storefronts. Use when starting any FastStore development task, writing TypeScript/React components, creating section overrides, extending the BFF, or styling. Covers all primary conventions, safety rules, and the development workflow used across every…
scraper-models
Cursor rule "scraper-models" from Solihatun1/AI-Cursor-Scraping-Assistant, covering scraper types, e-commerce plp, e-commerce pdp, how to fill the scraper fields with values and how to create an e-commerce plp scraper.