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/heimsmarkmidnpx skills add jokull/icelandic-data --skill heimsmarkmidgit 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/heimsmarkmid)<a href="https://agentmods.dev/skills/jokull/icelandic-data/heimsmarkmid"><img src="https://agentmods.dev/badge/skills/jokull/icelandic-data/heimsmarkmid.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.00028 | $0.01729 |
| Opus 5 | $0.00014 | $0.00864 |
| Sonnet 5 | $0.00006 | $0.00346 |
| Haiku 4.5 | $0.00003 | $0.00173 |
Grade A, and why
heimsmarkmid 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 4d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Heimsmarkmið — Iceland's UN Sustainable Development Goal statistics
Iceland's implementation of the UN 2030 Agenda. Hagstofa Íslands publishes
137 national SDG indicators (all 17 goals) via a public open-sdg instance.
- Site:
heimsmarkmidin.hagstofa.is(Icelandic) /heimsmarkmidin.hagstofa.is/en/(English) - Data repo:
hagstofan.github.io/heimsmarkmid-data-prod/(GitHub Pages) - Platform: open-sdg — same toolkit used by UK, US, and ~20 other national SDG portals. If you know one, you know all of them.
Architecture
Frontend is a server-rendered Jekyll static site. Underlying data and metadata are published as flat files on a sibling GitHub Pages repo:
| Path | Contents |
|---|---|
/is/data/{code}.csv |
Time-series data with disaggregation columns |
/is/meta/{code}.json |
Indicator metadata (name, source, graph config, units) |
/is/headline/{code}.csv |
Headline series only (no disaggregation) |
/is/comb/{code}.json |
Combined JSON (data + headline, structured for charting) |
/is/zip/all_indicators.zip |
All 137 data CSVs in one 437 KB download |
/en/... |
English-language mirror of the above |
Indicator codes follow the UN SDG nomenclature: goal-target-indicator, e.g.
1-1-1 (Goal 1 · Target 1 · Indicator 1) or 16-b-1 (target "b", indicator 1).
Usage
# Download the ZIP, extract to data/raw/heimsmarkmid/, build catalog CSV
uv run python scripts/heimsmarkmid.py fetch
uv run python scripts/heimsmarkmid.py fetch --force # Re-download (ZIP is cached)
# Print catalog
uv run python scripts/heimsmarkmid.py list
uv run python scripts/heimsmarkmid.py list --goal 4
# Fetch data + metadata for one indicator
uv run python scripts/heimsmarkmid.py get 1-1-1
uv run python scripts/heimsmarkmid.py get 16-b-1
The ZIP is fetched once and cached; metadata is fetched live on get (the
open-sdg meta endpoint doesn't ship inside the ZIP).
Catalog schema
data/processed/heimsmarkmid_catalog.csv:
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.
- 4d ago First seen · 144 lines · 28 tokens per session scan A 5e2146095a8c
heimsmarkmid is a skill published in the GitHub repository jokull/icelandic-data (52 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 1,729 once invoked, about $0.0001 per session on Opus 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.
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…