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 ThomasMoreAI/legal-skills-open --skill cultural-heritage-summarygit clone --depth 1 https://github.com/ThomasMoreAI/legal-skills-openWrote 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/thomasmoreai/legal-skills-open/cultural-heritage-summary)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/cultural-heritage-summary"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/cultural-heritage-summary/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/thomasmoreai/legal-skills-open/cultural-heritage-summary"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/cultural-heritage-summary.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.00097 | $0.01249 |
| Opus 5 | $0.00048 | $0.00624 |
| Sonnet 5 | $0.00019 | $0.00250 |
| Haiku 4.5 | $0.00010 | $0.00125 |
Grade A, and why
cultural-heritage-summary 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cultural Heritage Protection Summary
Produces a structured legal update on developments affecting cultural heritage protection across jurisdictions and tribunals.
Prerequisites
- Time window — exact start/end dates for the reporting period
- Scope — jurisdictions, tribunals, and administrative bodies to cover
- Audience — government, NGO, cultural institution, enforcement, or mixed
- Citation standard — Bluebook, OSCOLA, or organization-specific
- Source access — primary sources: decisions, statutes, treaties, official releases
Do not proceed without items 1–3. Ask if missing.
Quick Start
- Collect prerequisites and confirm scope with the user.
- Triage source materials by thematic section.
- Apply selection criteria to identify reportable developments.
- Draft each development using the entry template.
- Compile the executive overview, thematic sections, and trend analysis.
- Verify all citations and flag uncertainties with
[VERIFY].
Output Structure
Executive Overview (max 1 page)
- 5–10 bullet headlines of the most material developments.
- One-sentence implication per headline.
Thematic Sections
Include only sections supported by the source set:
- Repatriation and restitution
- Site and monument protection
- Illicit trafficking and enforcement
- Armed conflict and emergency protections
- Underwater cultural heritage
- Intangible cultural heritage and indigenous rights
- Cultural property in trade/customs and export controls
- Digital heritage and documentation
Selection Criteria
Include a development only when it meets at least one:
- Direct legal effect (binding decision, statute, regulation, treaty action)
- New interpretation or shift in enforcement posture
- Cross-border or precedent value
- High stakeholder impact
Development Entry Template
Title:
Jurisdiction / Forum:
Date:
Type: Decision / Statute / Regulation / Treaty / Policy
Parties / Actors:
Subject Matter:
Legal Framework: (1954 Hague; 1970 UNESCO; 1995 UNIDROIT; 2001 UCH; 2003 ICH; 1972 World Heritage; national statute)
Key Issue:
Holding / Outcome:
Reasoning Snapshot:
Practical Impact:
Cross-Jurisdiction Signal:
Citations:
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.
- 9d ago First seen · 138 lines · 97 tokens per session scan A 0630315c5045
cultural-heritage-summary is a skill published in the GitHub repository ThomasMoreAI/legal-skills-open (72 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 97 tokens to every session and 1,249 once invoked, about $0.0005 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-03.
Other skills, from other repositories
pia-generator
Generate structured privacy impact assessments so Claude can organize project privacy risks, controls, and decision points into a review-ready report.
audit-scope-checklist
Generate a scoped IT audit program with controls mapped to roles and compliance frameworks. Use this skill for audit planning, control checklist generation, and auditprogram.json creation.
compliance-checker
Compare system configuration evidence against common control frameworks and produce a concise compliance assessment with gaps and remediation priorities.
compliance-controls-playbook
Guide Claude through a structured compliance audit workflow covering framework selection, evidence planning, control testing, exception handling, and reporting.
evidence-tracker
Manage audit evidence requests, collection progress, and status reporting so Claude can keep audits organized and identify overdue or blocked evidence items.
consent-checker
Review privacy policy or notice text against common privacy frameworks so Claude can explain coverage gaps, strengths, and compliance priorities.