What is patent-pipeline?

A complete patent-drafting workflow that turns an invention description into a patent application for China, the United States, or Europe. It links prior-art research, novelty checking, claim writing, technical description, review, figures, and jurisdiction-specific formatting.

Use it to develop an invention into claims and a full specification, check earlier technical disclosures, prepare figures and embodiments, review the draft, and compile filing documents.

Writing a patent requires more than describing an idea: it must explain the invention, define its legal protection, and fit the target patent office’s rules. This workflow brings those tasks together in one process.

patent-pipeline — Skill for Claude Code by ThomasMoreAI

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 patent-pipeline

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/patent-pipeline/github.svg)](https://agentmods.dev/skills/thomasmoreai/legal-skills-open/patent-pipeline)

Your own site

<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/patent-pipeline"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/patent-pipeline/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/thomasmoreai/legal-skills-open/patent-pipeline"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/patent-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 3,608 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 94% 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.

Model	Per session	Once invoked
Fable 5.1	$0.00081	$0.03608
Opus 5.5	$0.00032	$0.01443
Sonnet 5.5	$0.00016	$0.00722
Haiku 4.5	$0.00008	$0.00361

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

Security

Grade A, and why

patent-pipeline 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

94% identical to patent-pipeline — 30 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/patent-pipeline/SKILL.md · 352 lines

How it starts

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

Patent Pipeline: From Invention to Filing

Draft a complete patent application based on: $ARGUMENTS

Overview

This skill orchestrates the full patent drafting lifecycle -- from prior art search through jurisdiction-formatted filing documents. It chains sub-skills into a patent-specific pipeline:

/prior-art-search → /patent-novelty-check → /invention-structuring → /claims-drafting → /specification-writing → /patent-review → /jurisdiction-format
     (search)           (verify)              (structure)             (claims)            (description)          (examiner)         (compile)
                                                                                              ├── /figure-description
                                                                                              └── /embodiment-description

This is a parallel branch, not part of the linear research pipeline. After /idea-discovery produces validated ideas, the user can either:

Go to /experiment-bridge → /auto-review-loop → /paper-writing (publish track)
Go to /grant-proposal (funding track)
Go to /patent-pipeline (patent track) <-- this skill

                    ┌→ /experiment-bridge → /auto-review-loop → /paper-writing  (publish track)
/idea-discovery ────┤
                    ├→ /grant-proposal → [get funded] → ...  (funding track)
                    └→ /patent-pipeline → [file patent]       (patent track)

Patents are about protecting inventions (legal scope), not publishing results (academic contribution). This skill handles the unique requirements of patent drafting: prior art analysis, claims hierarchy design, specification writing with enablement support, embodiment descriptions, and jurisdiction-specific formatting.

Constants

JURISDICTION = CN — Target patent jurisdiction. Options: CN (CNIPA), US (USPTO), EP (EPO), ALL (generate all three). Override via argument (e.g., /patent-pipeline "invention — US").
PATENT_TYPE = invention — invention (发明专利, 20 year protection) or utility_model (实用新型, CN only, 10 year protection, apparatus claims only). Override via argument.
REVIEWER_MODEL = gpt-5.5 — Model used via Codex MCP for examiner-style review.
MAX_REVIEW_ROUNDS = 2 — Maximum review-revision cycles.
AUTO_PROCEED = false — At each checkpoint, always wait for explicit user confirmation. Patent applications require inventor judgment at every stage. Set true only if user explicitly requests autonomous mode.
LANGUAGE = auto — Output language. Auto-detected from jurisdiction: CN->Chinese, US->English, EP->English. Override explicitly if needed.
OUTPUT_DIR = patent/ — Directory for generated patent files.
OUTPUT_FORMAT = markdown — Draft format. markdown for review, docx for filing-ready.

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

1mo ago First seen · 352 lines · 81 tokens per session scan A 1054941aa5dd

Subscribe to this mod's changes

patent-pipeline is a skill published in the GitHub repository ThomasMoreAI/legal-skills-open (95 stars, last pushed 15d ago), licensed Apache-2.0. It adds 81 tokens to every session and 3,608 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to patent-pipeline, differing in 30 lines, and is treated as a copy.

Claude Code Legal and compliance ai-agents anthropic-skills claude-skills compliance contract-analysis

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