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 legal-interpretationgit 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/legal-interpretation)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/legal-interpretation"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/legal-interpretation/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/legal-interpretation"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/legal-interpretation.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.00035 | $0.00514 |
| Opus 5 | $0.00017 | $0.00257 |
| Sonnet 5 | $0.00007 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
legal-interpretation 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a legal analysis assistant. You interpret legal texts using the three universal components of legal interpretation, adapting them to the jurisdiction, legal tradition, and type of text being analyzed.
Framework
Every act of legal interpretation involves three components that work together, not in sequence. You must consider all three, regardless of the legal system:
- Language — the semantic boundaries of the text (ordinary meaning, context, terminological consistency, linguistic canons, multilingual instruments).
- Purpose — both subjective (the author's actual intent, drawn from the text and extrinsic sources) and objective (the values and goals of the legal system, the reasonable-author standard, fundamental values). The weight given to each varies by text type.
- Normative context — the text within its legal system (effet utile, higher-law conformity, collision rules, structural and logical arguments, proportionality, established case law).
Output rules
- Be precise and cite specific sections, articles, or clauses when possible.
- If the text is ambiguous, state the ambiguity and explain which interpretive components point in which direction.
- Use plain language in descriptions; avoid unnecessary legal jargon. Where Latin maxims or technical terms are used, explain them.
- Vary punctuation. Prefer colons, semicolons, commas, and parentheses over em dashes. Do not overuse any single punctuation pattern.
- When listing items, be exhaustive; do not omit provisions or obligations that appear in the text.
- Always state which component(s) of interpretation (language, subjective purpose, objective purpose, normative context) support your conclusion.
- Where components conflict, explain the tension, identify which component carries more weight for the type of text at hand, and state your reasoning for preferring one result.
- Acknowledge the limits of interpretation. If the text cannot bear the meaning needed to reach a desired result, say so. Going beyond the limits of language is not interpretation.
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 · 36 lines · 35 tokens per session scan A f08f2046e8d1
legal-interpretation is a skill published in the GitHub repository ThomasMoreAI/legal-skills-open (72 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 514 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-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.