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 airbnbgit 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/airbnb)<a href="https://agentmods.dev/skills/agentcomputerai/torch/airbnb"><img src="https://agentmods.dev/badge/skills/agentcomputerai/torch/airbnb/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/airbnb"><img src="https://agentmods.dev/badge/skills/agentcomputerai/torch/airbnb.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.00121 | $0.02688 |
| Opus 5.5 | $0.00048 | $0.01075 |
| Sonnet 5.5 | $0.00024 | $0.00538 |
| Haiku 4.5 | $0.00012 | $0.00269 |
Grade A, and why
airbnb scanned grade A with 1 finding 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.
`curl -sL` returns 200 immediately. No challenge, no JS check, no cookies needed beyond what the response sets. How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Airbnb (airbnb.com)
Airbnb's search results page renders fully on the server and ships all listing data inline as JSON. There is no anti-bot wall on
/s/<location>/homes— a singlefetchwith a normal browser User-Agent returns HTTP 200 + ~900KB of HTML containing every listing on the page. Pagination is a flat list of opaque cursors discoverable from page 1.
Detection
| Signal | Value |
|---|---|
| CDN | Akamai (akamai-request-bc header) |
| Origin | nginx, x-instrumentation: airbnb |
| Framework | Custom Airbnb "Niobe" GraphQL client + React SSR |
| Anti-bot | None on /s/ HTML (Arkose Labs only on POST flows) |
| Auth | Not required for search |
| robots.txt | Allows /s/ for major UAs |
curl -sL returns 200 immediately. No challenge, no JS check, no cookies needed beyond what the response sets.
Architecture
- React SSR app shell at
/s/:location?/homes/:additionalRefinements?. - Search payload comes from the internal Niobe GraphQL endpoint (
StaysSearchoperation), but the SSR pass already inlines the response in the HTML. There is no need to replay the GraphQL endpoint. - The inlined JSON lives in one of two script tags depending on which render path served the request:
<script id="data-deferred-state-0">— streaming/deferred render. This is what plainfetchfrom Node usually gets. Path to listings:niobeClientData[0][1].data.presentation.staysSearch.results.searchResults.<script id="data-injector-instances">— fully inlined render (sometimes served tocurl/cached). Path to listings:root[3][1][2][1].data.presentation.staysSearch.results.searchResults.
- Both paths land at the same
presentation.staysSearch.resultsshape, so a stack-based walk that looks foro.staysSearch.results.searchResultsworks on either. - Each page returns 18 results in
searchResults. The map carousel (mapResults.mapSearchResults, ~20) overlaps but isn't needed. - Pagination is a flat list of base64 cursors at
staysSearch.results.paginationInfo.pageCursors(typically 15 cursors → ~270 listings cap per query). Append?cursor=<urlencoded base64>to the same URL.
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 · 172 lines · 121 tokens per session scan A a24023354652
airbnb is a skill published in the GitHub repository AgentComputerAI/torch (5 stars, last pushed 6mo ago), licensed MIT. It adds 121 tokens to every session and 2,688 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). 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.