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 government-journal-recordsgit 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/government-journal-records)<a href="https://agentmods.dev/skills/taivop/marketplace/government-journal-records"><img src="https://agentmods.dev/badge/skills/taivop/marketplace/government-journal-records/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/government-journal-records"><img src="https://agentmods.dev/badge/skills/taivop/marketplace/government-journal-records.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.00032 | $0.00444 |
| Opus 5 | $0.00016 | $0.00222 |
| Sonnet 5 | $0.00006 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
government-journal-records 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 12d 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
Government Office Journal Records
Access
- Series view:
GET https://dhs.riigikantselei.ee/avalikteave.nsf/byjournalkey?open - Public XML; no login or browser JavaScript is required.
Retrieve
The root response is an <entries> document containing <category> rows. Follow a category's URL or send its exact label as the path parameter:
?open&path=12-10%20Lepingud%20ja%20lepingutega%20seotud%20dokumendid
Use start for pagination. Read totalhits, start, count, from, to, and the next/end links from <entries> rather than assuming a page size.
Category results contain <document noteid="..." href="..."> rows and named <field> children. The root fieldtitles block maps field names to Estonian labels. Follow /avalikteave.nsf/documents/<noteid>?open for the public detail record.
Return
- Preserve category path,
noteid, detail URL, every named field, source URL, and retrieval time. - Common fields include
date,docid,subject,from,receivedfrom,sentto, document type, issuer, keywords, protocol number, meeting place, and contract dates. - Keep absent fields null; available fields vary by document series.
Limits
- This is an older Government Office document system and may overlap newer ADR records.
- Category labels have historical variants; do not merge them solely by numeric prefix.
- Detail records can omit restricted document content while retaining public metadata.
Verify
- Require HTTP 200
text/xmlwhose root isentries, with category links and paging attributes. - Require a known populated category to return document rows with
noteid,href,date,docid, andsubject.
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.
- 12d ago First seen · 39 lines · 32 tokens per session scan A 217c22c96c38
government-journal-records is a skill published in the GitHub repository taivop/marketplace (17 stars, last pushed 12d ago), licensed MIT. It adds 32 tokens to every session and 444 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-08-30.
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…
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…
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…