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-addressesgit 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-addresses)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-addresses"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-addresses/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-addresses"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-addresses.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.00184 | $0.02324 |
| Opus 5.5 | $0.00074 | $0.00930 |
| Sonnet 5.5 | $0.00037 | $0.00465 |
| Haiku 4.5 | $0.00018 | $0.00232 |
Grade A, and why
orchardcore-addresses 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CrestApps Addresses
Addresses (new in CrestApps.OrchardCore 3.0) gives the platform one address structure for every country. Each country's rules decide which parts it has, which are required, and how it is checked and printed. The data is a snapshot of Google's address data (CC BY 4.0) inside the package; a site never calls Google for formats.
Where it fits in the commerce suite
| Module | Relationship |
|---|---|
Shipping (orchardcore-shipping) |
Requires Addresses; zones and rates use Address |
Customers (orchardcore-customers) |
Address book edited with the address editor |
Checkout and Orders (orchardcore-checkout, orchardcore-orders) |
Contact and shipping steps, immutable order copies, printed with IAddressFormatter |
Taxation (orchardcore-taxation) |
Jurisdictions match region codes; country lists come from ICountryService |
CrestApps Content Fields (orchardcore-crestapps-content-fields) |
Address Field (CrestApps.OrchardCore.ContentFields.Address) on any content type |
Addresses depends on nothing and can be used outside commerce.
Features
| Feature ID | Name | Depends on |
|---|---|---|
CrestApps.OrchardCore.Addresses |
Addresses | none |
CrestApps.OrchardCore.Addresses.Countries |
Address Countries | Addresses, OrchardCore.Contents, OrchardCore.ContentFields, OrchardCore.Title |
CrestApps.OrchardCore.Addresses.GooglePlaces |
Address Suggestions (Google Places) | Addresses |
Guidelines
- Install
CrestApps.OrchardCore.Addressesin the web/startup project. - Store
Addressvalues, never free-text address strings, and keep a copy (Clone()) on records that must not change. - Store regions by code (
CA,13,D) so tax jurisdictions match;IAddressValidatortidies names into codes. - Validate posted addresses with
IAddressEditorService.ValidateAsyncand keep the returnedAddress. - Turn on
OrchardCore.RateLimitswherever a paid suggestion provider is set up. - All recipe JSON must be wrapped in
{ "steps": [...] }. - All C# classes must use the
sealedmodifier, except View Models.
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 · 176 lines · 184 tokens per session scan A 0f0db7f0b4ec
orchardcore-addresses is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed today), licensed MIT. It adds 184 tokens to every session and 2,324 once invoked, about $0.0007 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.