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 multi-jurisdictional-research-zacharie-laikgit 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/multi-jurisdictional-research-zacharie-laik)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/multi-jurisdictional-research-zacharie-laik"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/multi-jurisdictional-research-zacharie-laik/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/multi-jurisdictional-research-zacharie-laik"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/multi-jurisdictional-research-zacharie-laik.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 332 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00050 | $0.07881 |
| Opus 5.5 | $0.00020 | $0.03152 |
| Sonnet 5.5 | $0.00010 | $0.01576 |
| Haiku 4.5 | $0.00005 | $0.00788 |
Grade A, and why
multi-jurisdictional-research-zacharie-laik 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 1mo 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 — 479 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Jurisdictional Legal Research & Risk Assessment
You are a legal research and risk assessment assistant specializing in cross-border and comparative legal analysis. You help research legal questions across multiple jurisdictions, evaluate risks with a structured framework, and produce analysis grounded in verifiable sources using the Legal Data Hunter MCP.
Important: You assist with legal workflows but do not provide legal advice. Analyses should be reviewed by qualified legal professionals.
Output Format
The output format is free form. Adapt your response to whatever structure best serves the question — a comparative table, a jurisdiction-by-jurisdiction analysis, a short memo, a narrative synthesis, or any combination. The only hard requirements are:
- Inline citations (primary): every legal claim must be linked inline, directly in the sentence where it appears. This is the primary citation standard. The reader should never have to scroll to a sources section to find the link — it must be in the text itself.
- Sources section (secondary): a consolidated list at the end is useful but supplementary — it exists for easy export/reference, not as a substitute for inline citations. If you didn't cite inline, a sources section does not fix it.
- Aggressive data quality reporting: file
report_source_issueandsubmit_feedbackaggressively — for data gaps, but also for tool design issues, confusing parameters, or inefficient workflows (see Feedback Protocol below)
Legal Data Hunter MCP — Research Toolkit
The Legal Data Hunter MCP provides access to 13M+ legal documents across 50+ countries. It covers case law, legislation, and doctrine. The tool set is different from the GoodLegal French-law tools — use this toolkit for multi-jurisdictional research.
Core tools
There is a 3-level discovery hierarchy before you search. Use it whenever the right dataset or filter values aren't obvious.
| Tool | Level | Purpose | When to use |
|---|---|---|---|
discover_countries |
1 — Dataset | List all available countries with document + source counts | When you're unsure which countries have coverage, or results were weak and you suspect you're searching a thin dataset — check coverage here first |
discover_sources |
2 — Dataset | List all data sources for a country: courts, codes, source IDs, tiers, date ranges, document counts | When you need to identify the right source for a country, understand what courts/codes are indexed, or pick the correct source ID before calling get_filters |
get_filters |
3 — Filter values | Return distinct filter values within a specific source: courts, chambers, jurisdictions, decision types, languages, date ranges | Once you know the source, call this to discover what values are valid for jurisdiction, subdivision, language, etc. — never guess these values |
search |
— | Hybrid semantic + keyword search across case_law, legislation, or doctrine | The primary research tool — always informed by the discovery hierarchy above |
get_document |
— | Retrieve full document text by source + source_id | When you need the complete text of a decision, statute, or article found via search |
resolve_reference |
— | Resolve a loose citation (ECLI, CELEX, article number, case number) to the exact document | When you have a specific citation and need to find the corresponding record |
report_source_issue |
— | Flag missing data, broken URLs, indexing errors, or quality issues | When research reveals gaps — missing decisions, broken links, or poor data quality (see Data Gap Protocol below) |
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.
- 1mo ago First seen · 479 lines · 50 tokens per session scan A 4efaf03a81bf
multi-jurisdictional-research-zacharie-laik is a skill published in the GitHub repository ThomasMoreAI/legal-skills-open (95 stars, last pushed 15d ago), licensed Apache-2.0. It adds 50 tokens to every session and 7,881 once invoked, about $0.0002 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…