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 patent-pipeline-wanshuiyingit 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/patent-pipeline-wanshuiyin)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/patent-pipeline-wanshuiyin"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/patent-pipeline-wanshuiyin/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/patent-pipeline-wanshuiyin"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/patent-pipeline-wanshuiyin.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.00085 | $0.03606 |
| Opus 5 | $0.00043 | $0.01803 |
| Sonnet 5 | $0.00017 | $0.00721 |
| Haiku 4.5 | $0.00009 | $0.00361 |
Grade A, and why
patent-pipeline-wanshuiyin 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.
This is a copy
86% identical to patent-pipeline — 21 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.
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) orutility_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
trueonly 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.markdownfor review,docxfor filing-ready.
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 · 352 lines · 85 tokens per session scan A e56818d4036d
patent-pipeline-wanshuiyin is a skill published in the GitHub repository ThomasMoreAI/legal-skills-open (72 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 85 tokens to every session and 3,606 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to patent-pipeline, differing in 21 lines, and is treated as a copy.
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.