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/vedurnpx skills add jokull/icelandic-data --skill vedurgit 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/vedur)<a href="https://agentmods.dev/skills/jokull/icelandic-data/vedur"><img src="https://agentmods.dev/badge/skills/jokull/icelandic-data/vedur.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.00035 | $0.01608 |
| Opus 5 | $0.00017 | $0.00804 |
| Sonnet 5 | $0.00007 | $0.00322 |
| Haiku 4.5 | $0.00003 | $0.00161 |
Grade A, and why
vedur 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 -s "https://api.vedur.is/weather/capabilities" How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Veðurstofa Íslands (Icelandic Meteorological Office)
Weather observations, forecasts, climatological data and earthquakes for Iceland.
API — use api.vedur.is (JSON, OpenAPI)
Base URLs: https://api.vedur.is/weather · https://api.vedur.is/quakes
No authentication. JSON. Both are OpenAPI-described and browsable:
| Swagger UI | https://api.vedur.is/weather/ · https://api.vedur.is/quakes/ |
| Spec | https://api.vedur.is/weather/openapi.json (274 KB) · .../quakes/openapi.json |
| Versions seen | Weather 2026-02-17, Quakes 2026-07-01 |
The spec is authoritative, the summaries are not. GET /quakes/events is
summarised "Returns Quake Information As Geojson Or Csv", but format only
accepts csv|json — and json returns GeoJSON anyway. Read openapi.json
before believing prose.
Weather
# The cheapest liveness/shape check — 2.9 KB, lists every observation type
curl -s "https://api.vedur.is/weather/capabilities"
# Stations (776 of them, ~150 KB)
curl -s "https://api.vedur.is/weather/stations"
curl -s "https://api.vedur.is/weather/stations/1"
# Latest automatic-weather-station observations
curl -s "https://api.vedur.is/weather/observations/aws/10min/latest"
curl -s "https://api.vedur.is/weather/observations/aws/hour/latest"
# Parameter descriptions (what T, F, FX… mean)
curl -s "https://api.vedur.is/weather/parameters"
Aggregations: 10min, hour, day, month, year. There is also an OGC
EDR interface under /weather/rodeo/collections/{aggregation}/ with
locations, area and cube queries — worth reaching for if you want
standards-based spatial/temporal slicing rather than the bespoke endpoints.
Quakes (new — no equivalent in the old XML API)
# Events since a timestamp, magnitude filtered -> GeoJSON FeatureCollection
curl -s "https://api.vedur.is/quakes/events?start_time=2026-07-16T00:00:00&size_min=1"
# Just the count — returns a bare number, ideal for a cheap check
curl -s "https://api.vedur.is/quakes/events/count?start_time=2026-07-16T00:00:00"
curl -s "https://api.vedur.is/quakes/events/IMO2026nwqkrn" # one event
curl -s "https://api.vedur.is/quakes/regions" # seismic regions
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 · 155 lines · 35 tokens per session scan A 58a58cecb639
vedur is a skill published in the GitHub repository jokull/icelandic-data (52 stars, last pushed yesterday), licensed MIT. It adds 35 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
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…