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 agentmods add skills/apiliumcode/mayros/food-ordernpx skills add ApiliumCode/mayros --skill food-ordergit clone --depth 1 https://github.com/ApiliumCode/mayrosWrote 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/apiliumcode/mayros/food-order)<a href="https://agentmods.dev/skills/apiliumcode/mayros/food-order"><img src="https://agentmods.dev/badge/skills/apiliumcode/mayros/food-order.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 | $0.00034 | $0.00503 |
| Opus 5 | $0.00017 | $0.00251 |
| Sonnet 5 | $0.00007 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
food-order 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 3d 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.
This is a copy
92% identical to food-order — 21 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Food order (Foodora via ordercli)
Goal: reorder a previous Foodora order safely (preview first; confirm only on explicit user “yes/confirm/place the order”).
Hard safety rules
- Never run
ordercli foodora reorder ... --confirmunless user explicitly confirms placing the order. - Prefer preview-only steps first; show what will happen; ask for confirmation.
- If user is unsure: stop at preview and ask questions.
Setup (once)
- Country:
ordercli foodora countries→ordercli foodora config set --country AT - Login (password):
ordercli foodora login --email [email protected] --password-stdin - Login (no password, preferred):
ordercli foodora session chrome --url https://www.foodora.at/ --profile "Default"
Find what to reorder
- Recent list:
ordercli foodora history --limit 10 - Details:
ordercli foodora history show <orderCode> - If needed (machine-readable):
ordercli foodora history show <orderCode> --json
Preview reorder (no cart changes)
ordercli foodora reorder <orderCode>
Place reorder (cart change; explicit confirmation required)
- Confirm first, then run:
ordercli foodora reorder <orderCode> --confirm - Multiple addresses? Ask user for the right
--address-id(take from their Foodora account / prior order data) and run:ordercli foodora reorder <orderCode> --confirm --address-id <id>
Track the order
- ETA/status (active list):
ordercli foodora orders - Live updates:
ordercli foodora orders --watch - Single order detail:
ordercli foodora order <orderCode>
Debug / safe testing
- Use a throwaway config:
ordercli --config /tmp/ordercli.json ...
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.
- 3d ago First seen · 49 lines · 0 tokens per session scan A 7d595bf84b3e
food-order is a skill published in the GitHub repository ApiliumCode/mayros (12 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 503 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to food-order, differing in 21 lines, and is treated as a copy.
Other skills, from other repositories
after-sales
Use when managing post-purchase experience, building customer loyalty, or increasing repeat purchases.
convert-checkout-page
Author checkout-page micro-copy + trust signals: order summary, form-field copy, bump slot, button label, guarantee restatement, and friction-reduction patterns. Emits brief + paste-ready HTML/CSS scaffold (payment-processor-agnostic). Use when the user needs a conversion-optimized checkout page where every word and…
convert-bump
Author order-form bump offers: 30-80 word checkbox micro-copy that lifts AOV without breaking checkout flow. Emits brief + paste-ready HTML/CSS for the bump checkbox component. Use when the user has a checkout page and wants to add a single relevant low-friction bump above the buy button. Not for full upsell pages…
convert-oto-page
Author One-Time Offer pages: post-purchase upgrade with single accept/decline decision, urgency framing, and tight Method-applied copy. Emits brief + paste-ready HTML/CSS with one-click yes/no markup. Use when the user has a flagship product purchased and needs an immediate post-checkout upgrade page. Not for…
buy-a-product
Use this when someone wants to buy something from a Let Me Buy storefront — "buy a water at the bar", "order a coffee for table 9", "pay for the Jägermeister", "get me a drink from jonasbar". Covers picking the store, picking the product, deriving the accounts, and the traps that make a purchase land on the wrong…
campaign
Start, drive, monitor, and stop an Autonomous Improvement Campaign — a durable, repeatable wrapper around the dev-improve loop.