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-mapsnpx skills add imoonkey/openweb --skill google-mapsgit 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.00998 |
| Opus 5 | $0.00000 | $0.00499 |
| Sonnet 5 | $0.00000 | $0.00200 |
| Haiku 4.5 | $0.00000 | $0.00100 |
Grade A, and why
google-maps 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Maps
Overview
Google Maps — location search, place details, directions, and geocoding. Adapter-based extraction from internal APIs and SPA DOM.
Workflows
Find a place and get details
searchPlaces(query)→placeId, name, address, ratinggetPlaceDetails(placeId)→ name, address, rating, hours, website, phone, reviewsgetPlaceReviews(placeId)→ reviews with author, rating, relative timegetPlacePhotos(placeId)→ photo URLs with dimensionsgetPlaceHours(placeId)→ weekly operating schedulegetPlaceAbout(placeId)→ description, category, attributes
Steps 2–6 all use placeId from step 1.
Search nearby and compare
nearbySearch(category, location)→placeId, name, address, ratinggetPlaceDetails(placeId)per result → compare ratings, hours, prices
Get directions between locations
getDirections(origin, destination)→ driving routes with distance, durationgetTransitDirections(origin, destination)→ public transit routesgetWalkingDirections(origin, destination)→ walking routesgetBicyclingDirections(origin, destination)→ cycling routes
All are entry points — pick the travel mode needed.
Geocoding
geocode(address)→lat,lng,placeIdfrom address stringreverseGeocode(lat, lng)→ address, place name from coordinates
Operations
| Operation | Intent | Key Input | Key Output | Notes |
|---|---|---|---|---|
| searchPlaces | search places by query | query | placeId, name, address, rating, lat/lng | entry point, SPA nav |
| getPlaceDetails | full place details | placeId ← searchPlaces | name, rating, hours, website, phone, reviews | preview API |
| getPlaceReviews | detailed reviews | placeId ← searchPlaces | reviews[].text, authorName, rating, relativeTime | preview API |
| getPlacePhotos | photo URLs | placeId ← searchPlaces | photos[].url, width, height | preview API |
| getPlaceHours | operating schedule | placeId ← searchPlaces | status, schedule[].day, hours | preview API |
| getPlaceAbout | description + attributes | placeId ← searchPlaces | description, category, rating, website, phone | preview API |
| getDirections | driving directions | origin, destination | routes[].name, distanceText, durationText | entry point, SPA nav |
| getTransitDirections | transit directions | origin, destination | routes[].name, durationText | entry point, SPA nav |
| getWalkingDirections | walking directions | origin, destination | routes[].name, distanceText, durationText | entry point, SPA nav |
| getBicyclingDirections | cycling directions | origin, destination | routes[].name, distanceText, durationText | entry point, SPA nav |
| nearbySearch | search by category near location | category, location | placeId, name, address, rating, lat/lng | entry point, SPA nav |
| getAutocompleteSuggestions | type-ahead suggestions | input | suggestions[].text, placeId, description | entry point, suggest API |
| geocode | address to coordinates | address | lat, lng, placeId, formattedAddress | entry point, SPA nav |
| reverseGeocode | coordinates to address | lat, lng | address, name, placeId | entry point, SPA nav |
What ships with it
16 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-maps-api.ts 21 KB runs code
- DOC.md 7.7 KB
- examples/getAutocompleteSuggestions.example.json 215 B
- examples/getDirections.example.json 245 B
- examples/getPlaceDetails.example.json 266 B
- examples/getPlacePhotos.example.json 265 B
- examples/getPlaceReviews.example.json 266 B
- examples/getTransitDirections.example.json 278 B
- examples/getWalkingDirections.example.json 264 B
- examples/nearbySearch.example.json 234 B
- examples/reverseGeocode.example.json 215 B
- examples/searchPlaces.example.json 213 B
- manifest.json 1.3 KB
- openapi.yaml 28 KB
- pipeline-gaps.md 4.0 KB
- PROGRESS.md 5.2 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 · 82 lines · 0 tokens per session scan A 7efd743a3267
google-maps is a skill published in the GitHub repository imoonkey/openweb (56 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 998 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…