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 court-system-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/court-system-statistics)<a href="https://agentmods.dev/skills/taivop/marketplace/court-system-statistics"><img src="https://agentmods.dev/badge/skills/taivop/marketplace/court-system-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/court-system-statistics"><img src="https://agentmods.dev/badge/skills/taivop/marketplace/court-system-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.00023 | $0.00526 |
| Opus 5 | $0.00012 | $0.00263 |
| Sonnet 5 | $0.00005 | $0.00105 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
court-system-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 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
Court System Statistics
Access
- Index:
https://www.kohus.ee/eesti-kohtud/kohtute-menetlusstatistika - Main proceedings report:
https://app.fabric.microsoft.com/view?r=eyJrIjoiOWVjNWMxY2ItMDgwMS00NzhiLWIzOTctMDM5NTFlNjczNGE4IiwidCI6ImY2MzQyZDcwLWRhYzEtNDYxNC04ZTFhLTQ3YjkxYzE2YjhkZiIsImMiOjl9 - Payment-order report:
https://app.fabric.microsoft.com/view?r=eyJrIjoiOGQ5MmY3YWItZjM0Zi00OWNlLThjZWYtZDIzN2IyY2YwNmYwIiwidCI6ImY2MzQyZDcwLWRhYzEtNDYxNC04ZTFhLTQ3YjkxYzE2YjhkZiIsImMiOjl9
Retrieve
Use the index to discover the current public report IDs. In Fabric, set the year, court, court level, and proceeding type before copying or exporting a visual. Record every active filter with the extracted values.
Use https://www.riigikohus.ee/et/riigikohus/statistika for Supreme Court-specific totals and the index's historical link for 1997-2014 series. Court yearbooks are narrative context, not a substitute for the statistical report.
Return
- Preserve metric name, value, unit, period, court, court level, proceeding type, report URL, active filters, and retrieval time.
- Keep incoming cases, resolved cases, pending cases, duration, and clearance indicators distinct.
- Label values copied from a visual as dashboard extracts, not API records.
Limits
- No documented public REST contract is exposed for these reports.
- Fabric report IDs and visual schemas can change. Rediscover them from the index rather than relying only on a saved ID.
- Historical and current series may use different court structures or definitions.
Verify
- Require the index to link both public Fabric reports and the Supreme Court statistics page.
- Reject a blank Fabric shell as evidence that data was retrieved; require visible values or a successful export with recorded filters.
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 · 36 lines · 23 tokens per session scan A 0d2b9a2584f9
court-system-statistics is a skill published in the GitHub repository taivop/marketplace (17 stars, last pushed 12d ago), licensed MIT. It adds 23 tokens to every session and 526 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-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…