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/forgeyclap/claude-forge/forge-ecommercenpx skills add ForgeyClap/claude-forge --skill forge-ecommercegit clone --depth 1 https://github.com/ForgeyClap/claude-forgeWrote 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/forgeyclap/claude-forge/forge-ecommerce)<a href="https://agentmods.dev/skills/forgeyclap/claude-forge/forge-ecommerce"><img src="https://agentmods.dev/badge/skills/forgeyclap/claude-forge/forge-ecommerce.svg" alt="Measured on agentmods" 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 | $0.00044 | $0.01050 |
| Opus 5 | $0.00022 | $0.00525 |
| Sonnet 5 | $0.00009 | $0.00210 |
| Haiku 4.5 | $0.00004 | $0.00105 |
Grade A, and why
forge-ecommerce 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 5d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge playbook — E-commerce / store / digital products
Storefront UI defers to forge-website; anything that charges a card defers to forge-payments (this playbook never re-implements card handling). This file owns the commerce-specific concerns: catalog, cart, inventory correctness, orders, and connectors. Forge context: CASHFLOWWW / Moneymaker / Etsy-style shops.
Hard rules
- Real product/listing data with honest empty states. No lorem/placeholder products passed off as a real catalog; an empty catalog renders a real empty state, never fake inventory or fabricated sales/metrics.
- Oversell-safe inventory. Stock decrement is an atomic conditional update ("first writer wins",
UPDATE ... SET stock = stock - qty WHERE stock >= qty) or a reservation row — never a read-then-write that races. Concurrent buyers of the last unit → exactly one succeeds. Prefer soft-reserve at cart/checkout intake, hard-decrement at order confirmation. - Idempotent order creation.
POST /order(or checkout submit) carries anIdempotency-Keywith a UNIQUE constraint, because mobile networks retry, users double-tap, and gateways time out — a duplicate submit must return the same order, not create two. (Same pattern asforge-payments; keep them consistent.) - Connectors gated until keys + approval. Store/marketplace connectors (Shopify Admin, WooCommerce, Etsy, Stripe) stay disabled until real keys are present AND the owner approves. No live publish, store-push, listing update, price change, or spend without explicit owner approval.
- Money = integer minor units + currency (see
forge-payments); no float math on prices, tax, shipping, or discounts. - Secrets (store API keys, webhook secrets) in env +
.env.exampleplaceholders only.
Team (conditional)
Lead: build-boss (full store) or integration-boss (connector/sync-only). Specialists: payment-integration (checkout/charge — via forge-payments), database-reviewer (inventory + order schema, race-safety), silent-failure-hunter (a dropped inventory sync or swallowed order error looks like a clean sale), typescript-reviewer / python-reviewer. Storefront: forge-website team (a11y, responsive, real content). Optional: codex-reviewer on the checkout/order/inventory paths.
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.
- 5d ago First seen · 40 lines · 44 tokens per session scan A 048acbbdf911
forge-ecommerce is a skill published in the GitHub repository ForgeyClap/claude-forge (2 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 1,050 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
build-monetized-app
Use when the task is building a new app on Eliza Cloud that earns money — chat apps, agent apps, MCP-backed tools, anything that calls the cloud's chat/messages/inference endpoints on behalf of users. Covers app registration, container deploy, markup configuration, affiliate header, app charge requests, x402 payment…
eliza-cloud-buy-domain
Use whenever a user wants to register or buy a custom domain for an Eliza Cloud app — including in the same request as building the app ("build me X and put it on Y.com"). Uses Cloudflare as registrar after explicit user confirmation, paid from the user's existing cloud credit balance. Pairs with build-monetized-app…
ordercli
Foodora CLI for checking past orders and active order status. Use when the user asks to check food delivery orders, track a Foodora delivery, view order history, reorder a meal, look up past food orders, check delivery status, or manage Foodora sessions and authentication.
returns-policy
Answer return, refund, and warranty questions for electronics. Use when the user mentions returns, refunds, RMAs, warranty coverage, damaged items, or opened packaging.
integrations
One-request, complete setup of external services — payment (Stripe, PromptPay, Omise, 2C2P), email, auth, analytics, storage and other integrations, including Thai-market services. Installs SDKs, creates API routes, env templates, and UI components in one pass. Use when the user asks to add payments, email, login…
workflow-optimization
Read the customer request, account record, and supplied policies before choosing an action. Policy overrides the customer's requested remedy.