agentmods.dev

jurisdiction-format

jurisdiction-format is a skill for Claude Code from ThomasMoreAI/legal-skills-open. It costs 47 tokens per session (1,741 once invoked), scanned A, a copy of jurisdiction-format, Apache-2.0.

A formatter for turning a patent application into filing-ready documents for China, the United States, or Europe. It works from the patent’s claims, technical description, figures, and invention details.

In plain words
What is it for?
Use it to compile invention patent or Chinese utility-model applications for review in Markdown or for filing in DOCX.
Why use it?
Patent offices use different document structures and formatting rules, so one document may not fit every filing system. This helps organise the same invention for the chosen jurisdiction and output format.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

not rated 95repo +2 15d ago A scan 47 tokens copy · 89% Apache-2.0

Good fit Use it to compile invention patent or Chinese utility-model applications for review in Markdown or for filing in DOCX.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/thomasmoreai/legal-skills-open/jurisdiction-format
View source ↗ ThomasMoreAI/legal-skills-open
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 ThomasMoreAI/legal-skills-open --skill jurisdiction-format
Clone the repo
git clone --depth 1 https://github.com/ThomasMoreAI/legal-skills-open

Made for: Claude Code.

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.

agentmods badge for jurisdiction-format

README.md
[![agentmods](https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/jurisdiction-format/github.svg)](https://agentmods.dev/skills/thomasmoreai/legal-skills-open/jurisdiction-format)
Your own site
<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/jurisdiction-format"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/jurisdiction-format/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.

agentmods 80×15 button for jurisdiction-format

Your own site · 80×15
<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/jurisdiction-format"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/jurisdiction-format.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,741 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 89% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00047 $0.01741
Opus 5.5 $0.00019 $0.00696
Sonnet 5.5 $0.00009 $0.00348
Haiku 4.5 $0.00005 $0.00174

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

Security

Grade A, and why

jurisdiction-format 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.

Origin

This is a copy

89% identical to jurisdiction-format — 13 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

cross-jurisdiction/ip/skills/jurisdiction-format/SKILL.md · 200 lines

How it starts

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

Jurisdiction Format: Patent Filing Compilation

Compile the patent application into filing-ready format based on: $ARGUMENTS

Analogous to /paper-compile but for patent document formatting instead of LaTeX.

Constants

  • JURISDICTION = "auto" — From pipeline or args: CN, US, EP, ALL
  • PATENT_TYPE = "invention" — invention (发明专利) or utility_model (实用新型, CN only)
  • OUTPUT_FORMAT = "markdown" — markdown (for review) or docx (for filing, requires python-docx)
  • OUTPUT_DIR = "patent/output/" — Base output directory

Inputs

  1. patent/CLAIMS.md — drafted claims
  2. patent/specification/ — all specification sections (title, technical_field, background, summary, drawings_description, detailed_description, abstract)
  3. patent/figures/ — figure descriptions and numeral index
  4. patent/INVENTION_DISCLOSURE.md — for metadata

Shared References

Load ../shared-references/patent-format-cn.md for CNIPA document structure and formatting rules. Load ../shared-references/patent-format-us.md for USPTO document structure. Load ../shared-references/patent-format-ep.md for EPO document structure.

Workflow

Step 1: Determine Output Jurisdictions

From $ARGUMENTS or constant:

  • CN -> Generate CNIPA format only
  • US -> Generate USPTO format only
  • EP -> Generate EPO format only
  • ALL -> Generate all three formats

Step 2: Generate CN Format (if CN or ALL)

Output to patent/output/CN/:

权利要求书 (Claims)
  • Extract claims from patent/CLAIMS.md
  • Format per CNIPA conventions:
    • Independent claims: "1. 一种[主题]的方法，...其特征在于..."
    • Dependent claims: "2. 根据权利要求1所述的方法，其特征在于..."
  • Ensure Chinese terminology is correct (所述, 其特征在于, 包括, 等)
说明书 (Description)

Combine all specification sections in CNIPA order:

  1. 发明名称 (from title.md)
  2. 技术领域 (from technical_field.md)
  3. 背景技术 (from background.md)
  4. 发明内容 (from summary.md — split into 技术问题/技术方案/有益效果)
  5. 附图说明 (from drawings_description.md)
  6. 具体实施方式 (from detailed_description.md)

Read the full file on GitHub · 200 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.

  1. 1mo ago First seen · 200 lines · 47 tokens per session scan A 136e3b3273cd

Subscribe to this mod's changes

jurisdiction-format is a skill published in the GitHub repository ThomasMoreAI/legal-skills-open (95 stars, last pushed 15d ago), licensed Apache-2.0. It adds 47 tokens to every session and 1,741 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to jurisdiction-format, differing in 13 lines, and is treated as a copy.

Claude CodeLegal and complianceai-agentsanthropic-skillsclaude-skillscompliancecontract-analysis
Related

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens