patent-research-workflow

patent-research-workflow is a skill for Claude Code, Codex from smythmyke/patent-search-mcp-server. It costs 95 tokens per session (1,117 once invoked), scanned A, original, MIT.

A workflow for researching US patents, which are legal protections for inventions. It turns a patent number into information about its claims, ownership, history, challenges, lawsuits, and current legal status.

In plain words
What is it for?
Checking what a US patent covers, whether it is still active, who owns it, how it was examined, whether it faced challenges or lawsuits, and whether it may pose product risk.
Why use it?
It organizes several patent checks in the right order and starts with the least costly lookup that can answer the question. It covers US patents and USPTO file histories from 2001 onward.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: positional $N argument.

Good fit Checking what a US patent covers, whether it is still active, who owns it, how it was examined, whether it faced challenges or lawsuits, and whether it may pose product risk.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/smythmyke/patent-search-mcp-server/patent-research-workflow
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 smythmyke/patent-search-mcp-server --skill patent-research-workflow
Clone the repo
git clone --depth 1 https://github.com/smythmyke/patent-search-mcp-server

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.

agentmods badge for patent-research-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/smythmyke/patent-search-mcp-server/patent-research-workflow/github.svg)](https://agentmods.dev/skills/smythmyke/patent-search-mcp-server/patent-research-workflow)
Your own site
<a href="https://agentmods.dev/skills/smythmyke/patent-search-mcp-server/patent-research-workflow"><img src="https://agentmods.dev/badge/skills/smythmyke/patent-search-mcp-server/patent-research-workflow/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 patent-research-workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/smythmyke/patent-search-mcp-server/patent-research-workflow"><img src="https://agentmods.dev/badge/skills/smythmyke/patent-search-mcp-server/patent-research-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 95 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,117 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00095 $0.01117
Opus 5 $0.00048 $0.00558
Sonnet 5 $0.00019 $0.00223
Haiku 4.5 $0.00010 $0.00112

Measured 12d ago against content hash b4c1b519c34d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

patent-research-workflow 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 12d 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.

skills/patent-research-workflow/SKILL.md · 84 lines

How it starts

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

Patent Research Workflow

Guide for using the AI Patent Search Generator MCP connector to turn a US patent number into legal intelligence: bibliography, claims, prosecution history, PTAB validity challenges, district-court litigation, ownership chain, legal status, examiner statistics, and an AI risk verdict. All data is live from USPTO Open Data (US patents; file-wrapper coverage from 2001).

When to use this skill

Trigger when the user mentions: a US patent number (e.g. "US10867416B2", "patent 8,724,622"), "is this patent valid/alive/expired", "who owns this patent", "has this patent been challenged/litigated/sued over", "patent due diligence", "freedom to operate" (with the not-legal-advice caveat), "what are the claims of", "prosecution history / file wrapper", or "the examiner for this application".

Core workflow (patent number → intelligence)

  1. Normalize the number. Tools accept loose input ("10,867,416", "us10867416") and normalize to canonical form (US10867416B2). US patents only — say so if the user asks about EP/WO/CN numbers.

  2. Start with the question's cheapest sufficient tool (don't open with the dossier if a free lookup answers it):

    • "Still in force? When does it expire?" → legal_status (free)
    • "Who owns it? Chain of title?" → assignments (free)
    • "Was it attacked at the PTAB? Did it survive?" → challenges (free)
    • "What happened during examination?" → prosecution (free)
    • "Who sued whom over it?" → litigation (2 credits)
    • "How tough was the examiner?" → examiner (2 credits)
  3. Go deep with dossier (3 credits fresh, free from 24h cache) when the user wants the full picture: title, assignees, inventors, dates, status, independent claims, citations, family, CPC classes, similar documents. Use claims (1 credit cold, free cached) instead when they only need claim language — it's cheaper and returns every claim in full.

  4. One-shot verdict with risk_profile (40 credits fresh, free from 24h cache) when the user asks "how risky is this patent?" or wants due diligence: aggregates legal status + PTAB + litigation + ownership + term and returns Low/Moderate/High with a plain-English rationale and the underlying signals. Mention the cost before running it; repeat calls within 24 hours are free.

Read the full file on GitHub · 84 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. 12d ago First seen · 84 lines · 95 tokens per session scan A b4c1b519c34d

Subscribe to this mod's changes

patent-research-workflow is a skill published in the GitHub repository smythmyke/patent-search-mcp-server (2 stars, last pushed 3mo ago), licensed MIT. It adds 95 tokens to every session and 1,117 once invoked, about $0.0005 per session on Opus 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-31.

Related

Other skills, from other repositories

specification-writing

A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.

wanshuiyin/Auto-claude-code-research-in-sleep · 49 tokens

regulatory-research-fallback

Fallback workflow for regulatory research when web extraction tools fail on government PDFs.

HKUDS/OpenSpace · 20 tokens

x-scorecard

OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.

x-cmd/x-cmd · 57 tokens

gesellschaftsrechtliche-satzungen-agb

Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.

Klotzkette/claude-fuer-deutsches-recht · 69 tokens

memstack-business-gdpr

Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…

cwinvestments/memstack · 121 tokens

nda-review

Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…

LegalQuants/lq-ai · 79 tokens