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 opengeos/geoai-skills --skill overture-datagit clone --depth 1 https://github.com/opengeos/geoai-skillsWrote 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/opengeos/geoai-skills/overture-data)<a href="https://agentmods.dev/skills/opengeos/geoai-skills/overture-data"><img src="https://agentmods.dev/badge/skills/opengeos/geoai-skills/overture-data/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/opengeos/geoai-skills/overture-data"><img src="https://agentmods.dev/badge/skills/opengeos/geoai-skills/overture-data.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.00042 | $0.01003 |
| Opus 5.5 | $0.00017 | $0.00401 |
| Sonnet 5.5 | $0.00008 | $0.00201 |
| Haiku 4.5 | $0.00004 | $0.00100 |
Grade A, and why
overture-data 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 2mo 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are helping the user download Overture Maps data using geoai.
Input: $@
Follow these steps in order.
Step 1 -- Parse arguments
Extract:
$0or the first positional argument as the Overture data type--bbox minx,miny,maxx,maxyas the bounding box (required)--output FILEas the output file path (optional, default:./<data_type>_overture.gpkg)
Valid Overture data types:
address, building, building_part, division, division_area,
division_boundary, place, segment, connector, infrastructure,
land, land_cover, land_use, water
If the data type is not recognized, print the list of valid types and ask the user to pick one.
If the user provided natural language (e.g. "get buildings in downtown Nashville"), extract the data type and either infer or ask for the bounding box.
Step 2 -- Validate the bounding box
Confirm the bounding box has 4 numeric values:
minx < maxxandminy < maxy- Values within WGS84 range
If validation fails, report the issue and ask for corrected coordinates.
Step 3 -- Download the data
For building data specifically
python3 -c "
import geoai
gdf = geoai.download_overture_buildings(
bbox=(MINX, MINY, MAXX, MAXY),
output='OUTPUT_PATH',
)
print(f'Features: {len(gdf)}')
print(f'Columns: {list(gdf.columns)}')
print(f'CRS: {gdf.crs}')
print(f'Bounds: {gdf.total_bounds.tolist()}')
print('---')
print('Sample (first 5 rows):')
print(gdf.head().to_string())
"
For all other data types
python3 -c "
import geoai
gdf = geoai.get_overture_data(
overture_type='DATA_TYPE',
bbox=(MINX, MINY, MAXX, MAXY),
output='OUTPUT_PATH',
)
print(f'Features: {len(gdf)}')
print(f'Columns: {list(gdf.columns)}')
print(f'CRS: {gdf.crs}')
print(f'Bounds: {gdf.total_bounds.tolist()}')
print('---')
print('Sample (first 5 rows):')
print(gdf.head().to_string())
"
Replace DATA_TYPE, MINX, MINY, MAXX, MAXY, and OUTPUT_PATH with actual values.
Step 4 -- Update state
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.
- 2mo ago First seen · 131 lines · 42 tokens per session scan A ca80b4f1ec74
overture-data is a skill published in the GitHub repository opengeos/geoai-skills (35 stars, last pushed 25d ago), licensed MIT. It adds 42 tokens to every session and 1,003 once invoked, about $0.0002 per session on Opus 5.5. 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.
overture-data compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| overture-dataopengeos/geoai-skills | Skill | 35 | 25d ago | MIT | A | 42 | Claude Code |
| geoai-orchestratormuend/geoai-skills | Skill | 43 | 21d ago | MIT | A | 109 | Claude Code, Codex |
| google-earth-enginemuend/geoai-skills | Skill | 43 | 21d ago | MIT | A | 101 | Claude Code, Codex |
| point-cloud-lidarmuend/geoai-skills | Skill | 43 | 21d ago | MIT | A | 162 | Claude Code, Codex |
| postgis-spatial-sqlmuend/geoai-skills | Skill | 43 | 21d ago | MIT | A | 118 | Claude Code, Codex |
| change-detectionmuend/geoai-skills | Skill | 43 | 21d ago | MIT | A | 158 | Claude Code, Codex |
| geo-deep-learningmuend/geoai-skills | Skill | 43 | 21d ago | MIT | A | 104 | Claude Code, Codex |