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-point-of-salegit 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-point-of-sale)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-point-of-sale"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-point-of-sale/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-point-of-sale"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-point-of-sale.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.00198 | $0.02588 |
| Opus 5.5 | $0.00079 | $0.01035 |
| Sonnet 5.5 | $0.00040 | $0.00518 |
| Haiku 4.5 | $0.00020 | $0.00259 |
Grade A, and why
orchardcore-point-of-sale 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core Point of Sale - Prompt Templates
Sell at the Counter
You are an Orchard Core expert. Generate accurate setup, API and extension guidance for the CrestApps Point of Sale module, which sells at a store's counter from a till app over the commerce API. Each sale is an ordinary order paid through the checkout framework, so prices, coupons, gift cards, tax, stock holds, order events and reports work as online.
Guidelines
- Install
CrestApps.OrchardCore.PointOfSale(or theCrestApps.OrchardCore.Cms.Core.Targetsbundle) in the web/startup project. - Enable
CrestApps.OrchardCore.PointOfSale. It depends onCrestApps.OrchardCore.Commerce,CrestApps.OrchardCore.Orders,CrestApps.OrchardCore.InventoryandCrestApps.OrchardCore.Checkout.Api(the commerce JSON API, seeorchardcore-checkoutandorchardcore-commerce). - Products come from
CrestApps.OrchardCore.Products(seeorchardcore-products). Registers sell from Inventory locations. - Optional:
CrestApps.OrchardCore.Receiptsfor printable and emailed receipts,CrestApps.OrchardCore.Customersfor named buyers (seeorchardcore-customers), gift cards, andCrestApps.OrchardCore.Stripefor Stripe Terminal readers (seeorchardcore-payments). - Every API call is made by a signed-in staff member with a bearer token and Sell at a register. Send an
Idempotency-Keyheader on calls that take one, so a dropped connection never rings a sale twice. - Store credit and loyalty points are not offered at a register.
- Orders and stock locations are covered by
orchardcore-ordersandorchardcore-inventory; the shared Commerce menu byorchardcore-commerce. - All recipe JSON must be wrapped in
{ "steps": [...] }. - All C# classes must use the
sealedmodifier, except View Models.
Feature and Services
| Item | Value |
|---|---|
| Feature ID | CrestApps.OrchardCore.PointOfSale |
| YesSql collection | PointOfSale (Register/RegisterIndex, RegisterShift/RegisterShiftIndex) |
| Stores | IRegisterStore, IRegisterShiftStore |
| Services | PosShiftService (MaySellAtAsync, SummarizeAsync), PosSaleService (StartAsync, PayAsync, GetChange), PosReceipts |
| Cash tender | PosCashTenderProvider (ICheckoutTenderProvider, key cash) |
| Counter terminal | PosCounterCardPaymentProvider (ICheckoutPaymentProvider and ICheckoutPaymentRefundProvider, key pos-card) |
| Stripe reader | StripeTerminalPaymentProvider (key stripe-terminal), added by Stripe's TerminalStartup when both features are on |
| Session marker | CheckoutCounterSale (RegisterId, ShiftId, LocationId) |
| Order channel | OrderChannels.PointOfSale (pos); OrderChannels.IsCounterSale(order) |
| API | api/commerce/v1/pos/..., tag Point of Sale (PosApiEndpoints, StripeTerminalApiEndpoints) |
| Permissions | SellAtRegister, ManageRegisters (Administrator and Store manager have both) |
| Admin | Commerce > Point of sale > Registers (point-of-sale/registers) and Shifts (point-of-sale/shifts) on the AdminList standard |
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 · 129 lines · 198 tokens per session scan A 4bc96f823bc9
orchardcore-point-of-sale is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed today), licensed MIT. It adds 198 tokens to every session and 2,588 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.