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 AIDotNet/OpenCowork --skill luckin-orderinggit clone --depth 1 https://github.com/AIDotNet/OpenCoworkWrote 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/aidotnet/opencowork/luckin-ordering)<a href="https://agentmods.dev/skills/aidotnet/opencowork/luckin-ordering"><img src="https://agentmods.dev/badge/skills/aidotnet/opencowork/luckin-ordering.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.1 | $0.00063 | $0.00561 |
| Opus 5 | $0.00032 | $0.00280 |
| Sonnet 5 | $0.00013 | $0.00112 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
luckin-ordering 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 7d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Luckin Ordering Workflow
Order Luckin Coffee for store pickup using the My Coffee extension tools
(extension__my-coffee__*). Follow this workflow as a contract; the gates below exist because
the upstream API rejects out-of-order calls.
Preflight
- Run
check_token. If the token is missing, stop and walk the user through Settings -> Extensions -> My Coffee before anything else. - If tool parameters ever look stale or a call fails with a schema error, run
list_toolsand re-check the current schema before retrying.
Hard Rules
- Pickup only. For delivery requests, ask whether store pickup works instead; do not improvise a delivery flow.
- Never pick a store for the user. Show candidates from
query_shop_listand wait for an explicit choice. Only setlocationIsPrecise: truewhen the user gave exact coordinates. - Never guess SKUs. Customizations (temperature, sweetness, milk, size) go through
query_product_detailthenswitch_product; search results alone do not identify a SKU. preview_orderis a mandatory gate beforecreate_order: same store, same product list. The create call is rejected otherwise. Coupons returned by preview are passed through automatically.- Show only the payment QR (
payOrderQrCodeUrl) after creating an order. Show the pickup code only whenquery_order_detailreports the order is paid and returns pickup info. create_orderandcancel_orderare mutating actions; confirm intent with the user first.
Flow
- Ask what drink they want and roughly where they are (or reuse the store from earlier in the conversation).
query_shop_list-> user picks a store.search_productin that store -> if customization is requested,query_product_detail+switch_productto get the final SKU.preview_order-> confirm the final price with the user.create_order-> show the payment QR and tell the user to scan it.- On request,
query_order_detailfor status/pickup code;cancel_orderto cancel.
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.
- 7d ago First seen · 47 lines · 63 tokens per session scan A e5b31d5e782c
luckin-ordering is a skill published in the GitHub repository AIDotNet/OpenCowork (634 stars, last pushed 4d ago), licensed Apache-2.0. It adds 63 tokens to every session and 561 once invoked, about $0.0003 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-30.
Other skills, from other repositories
amazon-reviews-api-skill
This skill helps users automatically extract Amazon product reviews via the Amazon Reviews API. Agent should proactively apply this skill when users express needs like getting reviews for Amazon product with ASIN B07TS6R1SF, analyzing customer feedback for a specific Amazon item, getting ratings and comments for a…
amazon-competitor-analyzer
Scrapes Amazon product data from ASINs using browseract.com automation API and performs surgical competitive analysis. Compares specifications, pricing, review quality, and visual strategies to identify competitor moats and vulnerabilities.
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.
food-order
Reorder previous Foodora orders, preview cart contents, and track delivery ETA/status with ordercli. Use when the user wants to reorder food, check delivery status, or browse recent Foodora order history. Never confirm an order without explicit user approval.
product-description-generator
E-commerce product description generator for any platform. Generates optimized titles, bullet points, descriptions, and backend keywords using competitor research + keyword scoring + FABE copywriting. Two modes: (A) Create — generate listing from product specs with optional competitor analysis, (B) Optimize — improve…
amazon-price-tracker
Amazon price monitoring and competitive pricing intelligence. Real-time price tracking, Buy Box analysis, promotion detection, and dynamic pricing strategy optimization. Use when the user asks about price monitoring, competitor pricing, Buy Box tracking, or pricing strategy.