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 cultural-heritage-registergit 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/cultural-heritage-register)<a href="https://agentmods.dev/skills/taivop/marketplace/cultural-heritage-register"><img src="https://agentmods.dev/badge/skills/taivop/marketplace/cultural-heritage-register/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/cultural-heritage-register"><img src="https://agentmods.dev/badge/skills/taivop/marketplace/cultural-heritage-register.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00411 |
| Opus 5 | $0.00015 | $0.00205 |
| Sonnet 5 | $0.00006 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
cultural-heritage-register 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 13d 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
Cultural Heritage Register
Access
- Search and detail base:
https://register.muinas.ee/public.php?menuID=monument - The public server-rendered search works without authentication or browser automation.
Search
POST form data to the base URL. Prefer the precise fields when known:
regnr: cultural-monument registry number.name: monument name.address: address text.county[],parish[],type[], andcm_type[]: multi-value identifiers taken from the live form options.
For a broad text search, POST nameanddescription=<at least 3 characters> and quickseatch=true; the misspelled field name is the site's actual contract.
The result is HTML. Parse the table headed Reg. nr, Nimi, Tüüp, Liik, Omavalitsus, and Aadress. Each row links to:
public.php?menuID=monument&action=view&id={regnr}
Detail
Fetch the absolute detail URL and parse labeled fields. Return the registry number, name, monument type and class, registration/protection dates, coordinates, condition, legal instruments, keywords, descriptions, address when present, and links to available detail, property, proceeding, grant, image, and document tabs.
Limits
- Search and records are HTML, not JSON; decode HTML entities before extracting text.
- Multi-select filter values are internal IDs. Read them from the current search form instead of guessing from labels.
- A detail page can expose different tabs and fields by monument type.
Verify
Require the requested registry number in both the result row and detail heading, plus the detail labels Mälestise nimi and Mälestise registri number.
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.
- 13d ago First seen · 43 lines · 31 tokens per session scan A 17a592e26184
cultural-heritage-register 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 411 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…