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/imoonkey/openweb/google-flightsnpx skills add imoonkey/openweb --skill google-flightsgit clone --depth 1 https://github.com/imoonkey/openwebWhat 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.00000 | $0.00732 |
| Opus 5 | $0.00000 | $0.00366 |
| Sonnet 5 | $0.00000 | $0.00146 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
google-flights 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Flights
Overview
Flight search and pricing — adapter-based DOM extraction from rendered Google Flights pages.
Workflows
Search flights on a route
searchFlights(tfs)→flights[]with airline, times, price, stops, duration
Explore destinations from an origin
exploreDestinations()→destinations[]with flightPrice, dates, stops- Build
tfsfor a chosen destination →searchFlights(tfs)for specific flights
Compare search results with price insights
searchFlights(tfs)→ current flight options and pricesgetPriceInsights(tfs)→ cheapest/most expensive months, price trend, popular airlinesgetFlightOverview(tfs)→ cheapest fares and fastest nonstop for the route
All tfs-based operations share the same encoded route parameter (from the Google Flights URL).
Get booking details for a specific itinerary
searchFlights(tfs)→ pick a flightgetFlightBookingDetails(tfs)→ leg details, baggage policies, booking links
Operations
| Operation | Intent | Key Input | Key Output | Notes |
|---|---|---|---|---|
| searchFlights | search flights by route and dates | tfs (encoded route+dates) | origin, destination, flights[].airline, price, stops, duration | entry point; verified |
| getFlightOverview | cheapest fares and fastest flight for a route | tfs (encoded route) | cheapestOptions[].price, airline, fastestFlight, nonstopFrequency | entry point; same tfs |
| getFlightBookingDetails | itinerary details with baggage | tfs (encoded itinerary) | totalPrice, legs[].airline, duration, bagPolicies, bookWith | entry point; same tfs |
| exploreDestinations | browse destinations by budget from origin | — (optional tfs) | destinations[].destination, flightPrice, hotelPricePerNight, dates | entry point |
| getPriceInsights | monthly price trends and predictions | tfs (encoded route) | priceTrend, cheapestMonth, mostExpensiveMonth, popularAirlines | entry point; same tfs |
Quick Start
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- adapters/google-flights.ts 15 KB runs code
- DOC.md 6.7 KB
- examples/exploreDestinations.example.json 184 B
- examples/getFlightBookingDetails.example.json 350 B
- examples/getFlightOverview.example.json 329 B
- examples/getPriceInsights.example.json 343 B
- examples/searchFlights.example.json 340 B
- manifest.json 776 B
- openapi.yaml 15 KB
- pipeline-gaps.md 2.1 KB
- PROGRESS.md 1.9 KB
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.
- 2d ago First seen · 48 lines · 0 tokens per session scan A 2687c780494c
google-flights is a skill published in the GitHub repository imoonkey/openweb (58 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 732 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.