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 JansenAnalytics/claudex --skill food-ordergit clone --depth 1 https://github.com/JansenAnalytics/claudexWrote 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/jansenanalytics/claudex/food-order)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/food-order"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/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.1 | $0.00034 | $0.00532 |
| Opus 5 | $0.00017 | $0.00266 |
| Sonnet 5 | $0.00007 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
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
84% identical to food-order — 24 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 · 52 lines · 0 tokens per session scan A baedd3baa084
food-order is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 532 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to food-order, differing in 24 lines, and is treated as a copy.
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.