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 procurement-datagit 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/procurement-data)<a href="https://agentmods.dev/skills/taivop/marketplace/procurement-data"><img src="https://agentmods.dev/badge/skills/taivop/marketplace/procurement-data/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/procurement-data"><img src="https://agentmods.dev/badge/skills/taivop/marketplace/procurement-data.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.00024 | $0.00396 |
| Opus 5 | $0.00012 | $0.00198 |
| Sonnet 5 | $0.00005 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
procurement-data 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
Procurement Open Data
Use this source for tender notices, contract awards, and notice amendments. Use public-finance-data for budget totals without procurement detail.
Endpoints
- Register UI:
https://riigihanked.riik.ee/rhr-web/ - Procurement and modification notices:
https://riigihanked.riik.ee/rhr/api/public/v1/opendata/notice/{year}/month/{month}/xml - Contract, award, and modification notices:
https://riigihanked.riik.ee/rhr/api/public/v1/opendata/notice_award/{year}/month/{month}/xml
year is four digits and month is 1 through 12. The response is XML rooted at OPEN-DATA, although the server labels it application/vnd.ms-excel. Files can be tens of megabytes, so stream them to disk instead of loading them into memory.
Workflow
- Download both notice types for every required month.
- Parse XML with a namespace-aware parser. Notice schemas and namespaces vary by notice type and year.
- Keep the original notice identifier and type, publication and procedure dates, buyer and supplier identifiers/names, CPV codes, and estimated or awarded values when present.
- Distinguish procurement notices, awards, and amendments before aggregation. Do not treat estimated values as contract values.
- Record the canonical monthly URL and retrieval time with every extract.
Verification
- A valid response starts with an XML declaration followed by
OPEN-DATAandTED_ESENDERS. - The server supplies filenames such as
HT_2019_1.xmlfornoticeandHLST_2019_1.xmlfornotice_award.
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 · 30 lines · 24 tokens per session scan A 553dc3e4b8f6
procurement-data is a skill published in the GitHub repository taivop/marketplace (17 stars, last pushed 9d ago), licensed MIT. It adds 24 tokens to every session and 396 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…