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 AgentComputerAI/torch --skill ubereatsgit clone --depth 1 https://github.com/AgentComputerAI/torchWrote 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/agentcomputerai/torch/ubereats)<a href="https://agentmods.dev/skills/agentcomputerai/torch/ubereats"><img src="https://agentmods.dev/badge/skills/agentcomputerai/torch/ubereats/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/agentcomputerai/torch/ubereats"><img src="https://agentmods.dev/badge/skills/agentcomputerai/torch/ubereats.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.00108 | $0.01972 |
| Opus 5.5 | $0.00043 | $0.00789 |
| Sonnet 5.5 | $0.00022 | $0.00394 |
| Haiku 4.5 | $0.00011 | $0.00197 |
Grade A, and why
ubereats scanned grade A with 2 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
description: Proven scraping playbook for ubereats.com category pages (/category/<city>/<cuisine>). Fully server-rendered HTML behind Cloudflare, no anti-bot challenge on curl — plain GET returns every store card in the Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
import { execFile } from 'node:child_process'; How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Uber Eats (ubereats.com)
TL;DR
curl -sL --compressed <category_url> returns a fully rendered HTML page with every store card in the DOM. Parse with cheerio. Pagination is ?page=N, up to 4 pages (~21 stores/page) in a typical city/cuisine combo. No anti-bot defeats required.
Detection
| Signal | Value |
|---|---|
| CDN | Cloudflare (cf-ray, cf-cache-status: HIT) |
| Framework | Custom SSR — React hydration payload in <script type="application/json" id="__REDUX_STATE__"> |
| Anti-bot | None on /category/ pages via curl. __cf_bm cookie is set but not enforced. |
| Auth | Not required for SEO category pages |
| robots.txt | Allows /category/ |
Architecture
Uber Eats ships a React SPA, but the /category// routes are fully server-rendered for SEO. Every store card is in the initial HTML as:
<a data-testid="store-card" href="/store/<slug>/<storeUuid>">
<h3>Store Name</h3>
...
</a>
The parent div wraps: image (+srcset), name, ETA ("25 min"), price tier ("$", "$$"), optional promo badge ("Spend $35, Save $7"), and a "New" label (see Gotchas).
A window.__REDUX_STATE__ blob is also present but avoid it — it's embedded as a JSON-encoded string (with \u0022 for quotes) and contains a nested metaJson field that uses URL-encoding (%5C for backslash) which trips any stock JSON parser. Cheerio on the DOM is far cleaner.
Strategy used
- Phase 0 (curl) ✅ — HTTP 200, 1.2 MB HTML, all 21 store cards per page rendered inline. Done.
- Phase 1 — skipped (Phase 0 gate).
- Phase 2 — not needed.
Fetch — the one gotcha
Uber's content-security-policy header is ~40KB of whitelisted domains. Node's built-in fetch (undici) throws UND_ERR_HEADERS_OVERFLOW because its default header size cap is 16 KB. Two options:
- Shell out to
curl(simplest, what this skill uses). - Or use undici with a custom
Agent({ maxHeaderSize: 65536 }).
import { execFile } from 'node:child_process';
import { promisify } from 'node:util';
const execFileP = promisify(execFile);
async function fetchPage(url) {
const { stdout } = await execFileP(
'curl',
['-sL', '--compressed', '-A', UA, '-H', 'accept-language: en-US,en;q=0.9', url],
{ maxBuffer: 32 * 1024 * 1024 }
);
return cheerio.load(stdout);
}
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.
- 1mo ago First seen · 146 lines · 108 tokens per session scan A eb80b9c5a6cc
ubereats is a skill published in the GitHub repository AgentComputerAI/torch (5 stars, last pushed 6mo ago), licensed MIT. It adds 108 tokens to every session and 1,972 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
chrome-extension
Use when building or shipping a Manifest V3 browser extension and hitting its quirks — service worker dying and losing state, permission warnings, a Chrome Web Store rejection, content-script/worker/popup messaging, or an MV2-to-V3 migration. NOT a generic web app (that is nextjs), NOT a desktop shell (that is…
data-scraper
Use when data lives on a website with no usable API — listings, prices, public records — and the scrape must stay legal and not get blocked: legal gate, extraction path, durable selectors, pacing, resilience. NOT parsing bytes you already hold into fields (that is structured-extraction), NOT a documented API or key…
nodejs
Use when building or operating a plain Node.js / Express 5 backend service: project layout, async correctness, central error middleware, fail-fast config, graceful shutdown on SIGTERM. NOT DI modules/providers/guards (that is nestjs), NOT the type system or tsconfig (that is typescript), NOT REST contract design (that…
checking-a-page
Check that a web page you wrote or changed actually works, by opening it in a browser and driving every control on it. Use after creating or editing an HTML page, or the JavaScript or CSS that a page loads.
browser-qa
Testing web apps through a real browser: reconnaissance before acting, selector discovery, state capture, console errors and screenshot evidence. Use on a web surface end to end, or to reproduce a front-end bug.
browser-automation
A browser-automation workflow that detects the terminal environment and chooses a browser control tool. It supports opening pages, taking snapshots, clicking, filling fields, and other checks.