A legal research workflow that uses web searches and inline citations to investigate laws, regulations, market standards, and court decisions. It first identifies the relevant country or legal region and prioritizes authoritative sources.

Use it to research legal questions, regulatory requirements, industry norms, contract terms, or case law when jurisdiction-specific evidence and citations are needed.

It helps replace unsupported legal assumptions with information tied to official or institutional sources. It also adapts searches and explanations to the user's language and jurisdiction.

research — Skill for Claude Code and Codex by anylegal-ai/anylegal-oss

Install

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.

Any agent

npx skills add anylegal-ai/anylegal-oss --skill research

Clone the repo

git clone --depth 1 https://github.com/anylegal-ai/anylegal-oss

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/anylegal-ai/anylegal-oss/research/github.svg)](https://agentmods.dev/skills/anylegal-ai/anylegal-oss/research)

Your own site

<a href="https://agentmods.dev/skills/anylegal-ai/anylegal-oss/research"><img src="https://agentmods.dev/badge/skills/anylegal-ai/anylegal-oss/research/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/anylegal-ai/anylegal-oss/research"><img src="https://agentmods.dev/badge/skills/anylegal-ai/anylegal-oss/research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 942 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00032	$0.00942
Opus 5.5	$0.00013	$0.00377
Sonnet 5.5	$0.00006	$0.00188
Haiku 4.5	$0.00003	$0.00094

Measured 2mo ago against content hash 0f69d6b1a460, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

research 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 2mo 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.

backend/anylegal_oss/workspace/skills/research/SKILL.md · 77 lines

How it starts

The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Legal Research

When to Use

Use this skill when:

The user asks a legal question or wants to know about a law/regulation
The user says /research
The user asks about market standards, typical terms, or industry norms
The user needs jurisdiction-specific legal information
The user asks for regulatory guidance or compliance information

Process

Identify jurisdiction — infer from the question, document context, or session context. If ambiguous, ask the user.
Match language — search in the same language the user is writing in. If the user writes in Russian, use Russian-language search queries first (e.g., "ограничение ответственности SaaS договор"). Add English queries only as supplement if Russian results are insufficient.
Search authoritative sources first — use web_search with the jurisdiction set, targeting official government and institutional domains for statutory text, regulations, and case law. Frame queries with specific section/article numbers when known.
Read full pages with web_fetch — once you have URLs to authoritative sources, fetch them to get complete article/section text. Don't rely on search snippets for citations.
Cross-reference — for any cited statute or case, run a follow-up search to verify the citation is correct, current, and not superseded.
Supplement with secondary sources — use web_search for legal commentary, market standards, regulatory guidance, and practitioner analysis. Tag these as "commentary" rather than authority.
Synthesize the findings into a clear answer with inline citations.
Cite every factual claim using [[N]](URL) format. Start numbering from [1] in every new response or document — never continue numbering from earlier messages.

Output Format

Structure research responses as:

Answer: Direct, practical answer to the question with inline citations
Jurisdiction Context: Which jurisdiction this applies to and any cross-jurisdiction notes
Key Points: Bullet points of the most important findings, each cited
Practical Recommendations: What the user should do based on the research
Sources: Numbered list of all sources cited

Read the full file on GitHub · 77 lines

Changes

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.

2mo ago First seen · 77 lines · 32 tokens per session scan A 0f69d6b1a460

Subscribe to this mod's changes

research is a skill published in the GitHub repository anylegal-ai/anylegal-oss (17 stars, last pushed 24d ago), licensed MIT. It adds 32 tokens to every session and 942 once invoked, about $0.0001 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-08-30.

Legal and compliance Research

research next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
researchanylegal-ai/anylegal-oss	Skill	17	24d ago	MIT	A	32	Claude Code, Codex
fto-triageanthropics/claude-for-legal	Skill	9.9k	3d ago	Apache-2.0	A	81	Claude Code
legal-holdanthropics/claude-for-legal	Skill	9.9k	3d ago	Apache-2.0	A	68	Claude Code
specification-writingwanshuiyin/Auto-claude-code-research-in-sleep	Skill	19k	3d ago	MIT	A	49	Claude Code
terms-of-servicegenspark-ai/genoffice	Skill	12k	yesterday	Apache-2.0	A	32	Claude Code, Codex
x-scorecardx-cmd/x-cmd	Skill	4.7k	7d ago	Apache-2.0	A	57	Claude Code, Codex
gesellschaftsrechtliche-satzungen-agbKlotzkette/claude-fuer-deutsches-recht	Skill	1.8k	yesterday	Apache-2.0	A	69	Claude Code