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-checkoutgit 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-checkout)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-checkout"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-checkout/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-checkout"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-checkout.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.00203 | $0.05328 |
| Opus 5.5 | $0.00081 | $0.02131 |
| Sonnet 5.5 | $0.00041 | $0.01066 |
| Haiku 4.5 | $0.00020 | $0.00533 |
Grade A, and why
orchardcore-checkout 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 — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CrestApps Orchard Core Checkout
Checkout is the one path that takes money in the CrestApps commerce suite. Orders, subscriptions, transaction pay links, installment plans, bookings and the point of sale all start a checkout session through ICheckoutEngine; payment providers settle it; handlers decide what a completed checkout means. It is not a storefront: a consuming module contributes what is bought and reacts to the outcome.
Related skills: orchardcore-commerce (suite map and API conventions), orchardcore-payments (provider contracts, Stripe, refunds, installment plans), orchardcore-transactions (the ledger of money owed), orchardcore-pay-later (offline methods), orchardcore-carts and orchardcore-orders (the Order reference type), orchardcore-taxation, orchardcore-shipping, orchardcore-customers (Contact step, store credit, points).
Features
| Feature ID | Name | Adds | Depends on |
|---|---|---|---|
CrestApps.OrchardCore.Checkout |
Checkout | Engine, public checkout pages, payment endpoints, coupons, tenders, refund and reconciliation services, Settings > Commerce > Checkout | CrestApps.OrchardCore.Commerce |
CrestApps.OrchardCore.Checkout.TestProvider |
Test payments | Provider key test that confirms every payment without moving money |
Checkout |
CrestApps.OrchardCore.Checkout.Api |
Checkout API | Checkout endpoints in the commerce JSON API (api/commerce/v1) |
Checkout |
Feature IDs are constants on CheckoutConstants.Features (Area, TestProvider, Api). Install CrestApps.OrchardCore.Checkout and at least one provider module (Stripe, Pay Later) in the web/startup project. A module that only builds on checkout references CrestApps.OrchardCore.Checkout.Abstractions (contracts) and, for step drivers, CrestApps.OrchardCore.Checkout.Core.
{
"steps": [
{
"name": "Feature",
"enable": [
"CrestApps.OrchardCore.Checkout",
"CrestApps.OrchardCore.Checkout.TestProvider"
],
"disable": []
}
]
}
What ships with it
2 files 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 · 319 lines · 203 tokens per session scan A e9081dcf47fd
orchardcore-checkout is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed today), licensed MIT. It adds 203 tokens to every session and 5,328 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.