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 metaspartan/cybara --skill food-ordergit clone --depth 1 https://github.com/metaspartan/cybaraWrote 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/metaspartan/cybara/food-order)<a href="https://agentmods.dev/skills/metaspartan/cybara/food-order"><img src="https://agentmods.dev/badge/skills/metaspartan/cybara/food-order/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/metaspartan/cybara/food-order"><img src="https://agentmods.dev/badge/skills/metaspartan/cybara/food-order.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.00000 | $0.00503 |
| Opus 5 | $0.00000 | $0.00251 |
| Sonnet 5 | $0.00000 | $0.00101 |
| Haiku 4.5 | $0.00000 | $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 11d 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
89% identical to food-order — 28 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.
- 11d ago First seen · 42 lines · 0 tokens per session scan A e3803fed8148
food-order is a skill published in the GitHub repository metaspartan/cybara (28 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 503 tokens. A static security scan graded it A with 0 findings. It is 89% identical to food-order, differing in 28 lines, and is treated as a copy.
Other skills, from other repositories
build-monetized-app
Use when the task is building a new app on Eliza Cloud that earns money — chat apps, agent apps, MCP-backed tools, anything that calls the cloud's chat/messages/inference endpoints on behalf of users. Covers app registration, container deploy, markup configuration, affiliate header, app charge requests, x402 payment…
eliza-cloud-buy-domain
Use whenever a user wants to register or buy a custom domain for an Eliza Cloud app — including in the same request as building the app ("build me X and put it on Y.com"). Uses Cloudflare as registrar after explicit user confirmation, paid from the user's existing cloud credit balance. Pairs with build-monetized-app…
ordercli
Foodora CLI for checking past orders and active order status. Use when the user asks to check food delivery orders, track a Foodora delivery, view order history, reorder a meal, look up past food orders, check delivery status, or manage Foodora sessions and authentication.
personal-shopper
Personal advisor for a problem that might be solved by buying something — diagnoses the real need through conversation, then recommends products from the user's configured stores only when a purchase is the right answer. Recalls the user's sizes, budget, brands and restrictions across sessions, and records new ones as…
returns-policy
Answer return, refund, and warranty questions for electronics. Use when the user mentions returns, refunds, RMAs, warranty coverage, damaged items, or opened packaging.
capacitor-in-app-purchases
Guides the agent through setting up in-app purchases in Capacitor apps. Covers App Store Connect and Google Play Console product configuration, plugin selection (Capawesome Purchases vs. RevenueCat), plugin installation and platform setup, purchase flows for subscriptions and consumables, receipt validation, restore…