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 CrestApps/CrestApps.AgentSkills --skill orchardcore-ordersgit clone --depth 1 https://github.com/CrestApps/CrestApps.AgentSkillsWrote 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/crestapps/crestapps.agentskills/orchardcore-orders)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-orders"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-orders/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/skills/crestapps/crestapps.agentskills/orchardcore-orders"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-orders.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.00210 | $0.02669 |
| Opus 5.5 | $0.00084 | $0.01068 |
| Sonnet 5.5 | $0.00042 | $0.00534 |
| Haiku 4.5 | $0.00021 | $0.00267 |
Grade A, and why
orchardcore-orders 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CrestApps Orders
Orders (new in CrestApps.OrchardCore 3.0) checks a cart out through the Checkout framework and records what was bought. An order holds lines, not money: the payment, tax, attempts and refunds belong to the checkout session the order names.
Where it fits in the commerce suite
| Module | Relationship |
|---|---|
Carts (orchardcore-carts) |
Required. The cart is frozen into a draft order. |
Checkout (orchardcore-checkout) |
Required. Takes payment, coupons, tenders and tax for the order. |
Payments, Pay Later, Transactions (orchardcore-payments, orchardcore-pay-later, orchardcore-transactions) |
Collect and refund the money |
Customers (orchardcore-customers) |
Adds the Contact step, links Order.CustomerId, store credit refunds |
Inventory (orchardcore-inventory) |
Holds, sells, releases and restocks through order events |
Shipping (orchardcore-shipping) |
Adds the Shipping step, Order.Shipping, shipments and FulfillmentStatus |
Taxation (orchardcore-taxation) |
Tax lines copied to Order.TaxLines |
Receipts (orchardcore-receipts) |
ReceiptSettings brand invoices and packing slips |
Features
| Feature ID | Name | Depends on |
|---|---|---|
CrestApps.OrchardCore.Orders |
Orders | Commerce, Carts, Checkout, CrestApps.OrchardCore.Resources |
CrestApps.OrchardCore.Orders.GiftCards |
Gift Cards | Orders, OrchardCore.Title |
CrestApps.OrchardCore.Orders.Returns |
Returns | Orders |
CrestApps.OrchardCore.Orders.Api |
Orders API | Orders, Cart API, Checkout API |
Guidelines
- Install
CrestApps.OrchardCore.Ordersin the web/startup project and enable a payment provider. - React to orders with
IOrderEventHandler; never poll order status. - Cancel only through
IOrderService.CancelAsync, and refund throughOrderOperationsService, so every handler and ledger stays in step. - Send customer emails through
ICommerceEmailSenderso the store's templates, layout and the buyer's culture apply. - Resolve services that need
IOrderServicefromIServiceProviderinside the handler method to avoid a dependency cycle. - All recipe JSON must be wrapped in
{ "steps": [...] }. - All C# classes must use the
sealedmodifier, except View Models.
What ships with it
1 file 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.
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 First seen · 190 lines · 210 tokens per session scan A 25cd0ff21d47
orchardcore-orders is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed today), licensed MIT. It adds 210 tokens to every session and 2,669 once invoked, about $0.0008 per session on Opus 5.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-10-22.
Other skills, from other repositories
escalation
Escalate a disputed refund to the billing lead.
sfcc-platform-limits
Cheat-sheet and design patterns for surviving SFCC quotas and limits (script timeouts, HTTPClient call caps, session size, custom object quotas, file I/O restrictions, and headless rate limits). Use this when debugging enforced quota violations or designing scalable SFCC architectures.
broker-schedule
Repricing schedule management. Sets the interval for automatic price research and repricing, and registers the system-level scheduler (launchd on macOS, cron on Linux). Use when user wants to set or change the repricing interval, or invoke /broker-schedule to view/manage existing schedules. Default interval: 7 days.
a1-yandex-kit-promotions
Manage promotions in a Yandex KIT store over its REST API: discounts, promo codes, promocode groups (shared codes and single-use coupon batches) and gifts. Use when creating or updating discounts, promocodes, promocode groups or gifts, or when binding them to products, categories or collections. Russian triggers…
a1-yandex-kit-catalog-doctor
A tool for auditing and repairing Yandex KIT product catalogues. Yandex KIT is an e-commerce system for managing products, orders, discounts, and related catalogue data.
verify
How to verify changes to the a1-yandex-kit-setup helper CLI at its real surface (setup.mjs), including the no-network sandbox scenario.