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-session-agendasgit 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-session-agendas)<a href="https://agentmods.dev/skills/taivop/marketplace/government-session-agendas"><img src="https://agentmods.dev/badge/skills/taivop/marketplace/government-session-agendas/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-session-agendas"><img src="https://agentmods.dev/badge/skills/taivop/marketplace/government-session-agendas.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.00031 | $0.00508 |
| Opus 5 | $0.00015 | $0.00254 |
| Sonnet 5 | $0.00006 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
government-session-agendas 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 Session Agendas
Access
- Search page:
https://valitsus.ee/otsing?filters%5Btype%5D=Uudis&filters%5Bkeyword%5D=Istungi%20p%C3%A4evakord&sort=created&page=1 - Search API:
GET https://search.service.eu-live.vportal.ee/v1/search/valitsus - Public JSON; send
Origin: https://valitsus.eeand ahttps://valitsus.ee/referer.
Retrieve
Use API parameters:
query=Istungi päevakordfilters[type]=Uudissort_by=createdpage=1(one-based),limit=10langcode=ettimezone=Europe/Tallinn
Read response.numFound, response.start, and response.docs. Each result includes title, uri, created, lead_text, content fragments, content type, language, and highlighted matches. Resolve uri against https://valitsus.ee and fetch the article for the complete ordered agenda.
Agenda articles identify numbered items, presenter (Esitaja), type (Tüüp), and explanatory summary. Keep post-session Istung läbi announcements separate from pre-session kommenteeritud päevakord records.
Return
- Return session date, publication timestamp, agenda status, item number/title, presenter, draft type, summary, article URL, and retrieval time.
- Preserve the article's warning when an agenda is unconfirmed and may change.
- Link adopted legal acts through
legal-acts-datainstead of treating the agenda summary as final law.
Limits
- The search API is full-text search, so query results include related post-session communications.
- Search result content can be truncated; use the article page for complete agenda items.
- The keyword taxonomy count is not a count of distinct cabinet sessions.
Verify
- Require HTTP 200 JSON with positive
numFoundand nonemptydocsfor the documented query. - Require at least one result title containing
istungiandpäevakord, withuri,created, and content fields.
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 · 45 lines · 31 tokens per session scan A 6d3a07ab387b
government-session-agendas is a skill published in the GitHub repository taivop/marketplace (17 stars, last pushed 12d ago), licensed MIT. It adds 31 tokens to every session and 508 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…