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/jokull/icelandic-data/lminpx skills add jokull/icelandic-data --skill lmigit clone --depth 1 https://github.com/jokull/icelandic-dataWrote 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/jokull/icelandic-data/lmi)<a href="https://agentmods.dev/skills/jokull/icelandic-data/lmi"><img src="https://agentmods.dev/badge/skills/jokull/icelandic-data/lmi.svg" alt="Measured on agentmods" 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 | $0.00032 | $0.01608 |
| Opus 5 | $0.00016 | $0.00804 |
| Sonnet 5 | $0.00006 | $0.00322 |
| Haiku 4.5 | $0.00003 | $0.00161 |
Grade A, and why
lmi 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 5d 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 "https://gis.lmi.is/geoserver/ERM/wfs?service=WFS&version=2.0.0&request=GetFeature&typeName=ERM:Landmask&outputFormat=application/json&srsName=EPSG:4326" > Landmask.geojson 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.
LMI (Landmælingar Íslands) — National Land Survey
Vector geodata for Iceland mapping via GeoServer WFS. Pre-cached layers in data/geodata/ for fast map generation.
API
Base URL: https://gis.lmi.is/geoserver/{workspace}/wfs
No authentication required. WFS 2.0.0 protocol. Supports GeoJSON, GML, KML, Shapefile, GeoPackage output.
Workspaces
| Workspace | Description | Scale |
|---|---|---|
ERM |
EuroRegionalMap — core topographic vectors | 1:250,000 |
EBM |
EuroBoundaryMap — administrative boundaries | 1:100,000 |
ni |
Náttúrufræðistofnun — geology, nature, vegetation | 1:600,000 |
LMI_vektor |
Misc — municipalities, volcanic hazards, contours | varies |
LHG |
Landhelgisgæslan — maritime zones, depth contours | varies |
WFS Request Pattern
https://gis.lmi.is/geoserver/{workspace}/wfs?service=WFS&version=2.0.0&request=GetFeature&typeName={layer}&outputFormat=application/json&srsName=EPSG:4326
Example
curl "https://gis.lmi.is/geoserver/ERM/wfs?service=WFS&version=2.0.0&request=GetFeature&typeName=ERM:Landmask&outputFormat=application/json&srsName=EPSG:4326" > Landmask.geojson
Pre-Cached Core Layers
Downloaded via uv run python scripts/lmi.py download into data/geodata/:
| Layer | Features | Size | Use |
|---|---|---|---|
ERM:Landmask |
104 | 1.0 MB | Iceland land polygon (base fill) |
ERM:CoastalLine |
123 | 1.0 MB | Coastline outline |
EBM:AdministrativeUnit_level2 |
128 | 4.1 MB | Municipalities with names (namn field) |
ERM:AdministrativeAreas |
2,713 | 5.6 MB | Small admin zones (code-based, no names) |
ERM:RoadLines |
2,918 | 3.4 MB | Road network (classified by rtt) |
ERM:WatercourseLine |
28,536 | 27.2 MB | Rivers and streams |
ERM:Lake_Reservoir |
2,376 | 5.2 MB | Lakes and reservoirs |
ERM:LandIceArea |
188 | 0.8 MB | Glaciers (jöklar) |
ERM:BuiltupAreaPoints |
98 | 0.1 MB | Settlements with population (ppl field) |
ERM:BuiltupArea |
22 | 0.0 MB | Urban area polygons |
ERM:NamedLocation_gnamel |
616 | 0.3 MB | Place names |
ERM:IslandArea |
281 | 0.5 MB | Islands |
ERM:Airport_Airfield_points |
61 | 0.0 MB | Airports |
ERM:Port |
11 | 0.0 MB | Harbors |
ERM:NatureParkArea |
40 | 0.7 MB | National parks and reserves |
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.
- 5d ago First seen · 131 lines · 32 tokens per session scan A 772650a392cd
lmi is a skill published in the GitHub repository jokull/icelandic-data (52 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 1,608 once invoked, about $0.0002 per session on Opus 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-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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…