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 x-road-usage-statisticsgit 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/x-road-usage-statistics)<a href="https://agentmods.dev/skills/taivop/marketplace/x-road-usage-statistics"><img src="https://agentmods.dev/badge/skills/taivop/marketplace/x-road-usage-statistics/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/x-road-usage-statistics"><img src="https://agentmods.dev/badge/skills/taivop/marketplace/x-road-usage-statistics.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.00035 | $0.00387 |
| Opus 5 | $0.00017 | $0.00193 |
| Sonnet 5 | $0.00007 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
x-road-usage-statistics 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 6d 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
X-Road Usage Statistics
Access
- Dashboard:
https://x-tee.ee/stats/ - Current production snapshot:
https://x-tee.ee/stats/EE/environmentData.json - Production history:
https://x-tee.ee/stats/EE/history.json - Public static JSON; no login is required.
Retrieve
Fetch environmentData.json for the current snapshot. It contains:
instanceIdentifierand datadatemembers,subsystems, andsecurityServersmemberClasses, withmemberClassandmemberCount
Fetch history.json for periodic snapshots with the same totals and member-class breakdown. Development and test environments use sibling ee-dev/ and ee-test/ paths; use EE/ for production.
Return
- Return one row per snapshot date and environment with all three totals.
- Keep member-class counts as a child table or expand
COM,GOV,NGO, andNEEinto explicit columns. - Include the JSON URL and retrieval time; use the payload's
dateas the observation date.
Limits
- These datasets count infrastructure and participants, not X-Road requests or transaction volume.
- History frequency is determined by the publisher and may not be daily.
- The old
/facts-and-figures/URL now redirects to the X-Road self-service homepage and is not a data source.
Verify
- Require the current endpoint to return an
EEJSON object with a parseable date and positive integer totals. - Require history to be a nonempty chronological JSON array with the same metric keys.
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.
- 6d ago First seen · 41 lines · 35 tokens per session scan A db07780b9127
x-road-usage-statistics is a skill published in the GitHub repository taivop/marketplace (17 stars, last pushed 10d ago), licensed MIT. It adds 35 tokens to every session and 387 once invoked, about $0.0002 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…