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 taivop/marketplace --skill statistics-apigit clone --depth 1 https://github.com/taivop/marketplaceWrote 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/taivop/marketplace/statistics-api)<a href="https://agentmods.dev/skills/taivop/marketplace/statistics-api"><img src="https://agentmods.dev/badge/skills/taivop/marketplace/statistics-api/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/taivop/marketplace/statistics-api"><img src="https://agentmods.dev/badge/skills/taivop/marketplace/statistics-api.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00023 | $0.00455 |
| Opus 5 | $0.00012 | $0.00228 |
| Sonnet 5 | $0.00005 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
statistics-api 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 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.
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.
What it actually says
Statistics Estonia API
Access
Public PXWeb JSON API. No authentication. Use https://andmed.stat.ee/api/v1/en/stat for English or replace en with et for Estonian.
Retrieve
- Discover folders and tables with
GET /api/v1/en/stat; descend by appending returned folder IDs. - Fetch a table contract with
GET /api/v1/en/stat/{TABLE_ID}. It returnstitleandvariables; use each variable'scodeand allowedvaluesin the query. - POST the query to the same table URL:
{
"query": [
{"code": "Aasta", "selection": {"filter": "item", "values": ["2025"]}}
],
"response": {"format": "json-stat2"}
}
- Request with
Content-Type: application/json. Usecsv,json-stat2, or another format accepted by the table service. - When methodology matters, run
python get_metadata.py TABLE_ID --format textfrom this directory.
Working sample: GET https://andmed.stat.ee/api/v1/en/stat/IA001, then POST the payload above. The response is JSON-stat 2 with table ID IA001, year 2025, and a numeric value.
Return
Preserve the table ID, source and update metadata, dimension codes and labels, selected values, units/decimals, observations, exact POST payload, and retrieval time.
Limits
- The API root itself returns 404; include the language and database path.
- Table IDs are not enough to construct a query: always read the current variable contract first.
- Confirm units, seasonal adjustment, reference period, and suppression markers before analysis.
Verify
Require HTTP 200 JSON, variables in the table contract, and matching id, dimension, size, and value fields in a JSON-stat response. A portal HTML page or API-base 404 is not successful retrieval.
What ships with it
1 file 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.
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 · 45 lines · 23 tokens per session scan A 11ac71d81aae
statistics-api is a skill published in the GitHub repository taivop/marketplace (17 stars, last pushed 9d ago), licensed MIT. It adds 23 tokens to every session and 455 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-09-04.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…