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 Raw1mage/patentmcp --skill patent-searchgit clone --depth 1 https://github.com/Raw1mage/patentmcpWrote 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/raw1mage/patentmcp/patent-search)<a href="https://agentmods.dev/skills/raw1mage/patentmcp/patent-search"><img src="https://agentmods.dev/badge/skills/raw1mage/patentmcp/patent-search/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/raw1mage/patentmcp/patent-search"><img src="https://agentmods.dev/badge/skills/raw1mage/patentmcp/patent-search.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.00037 | $0.00577 |
| Opus 5 | $0.00018 | $0.00289 |
| Sonnet 5 | $0.00007 | $0.00115 |
| Haiku 4.5 | $0.00004 | $0.00058 |
Grade A, and why
patent-search 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 10d 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
97% identical to patent-search — 2 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Patent Search Skill
This skill points Claude at the BigQuery patent-search tools registered by the patent-creator MCP server. Call the tools directly; do not shell out to Python.
When to use
- Find prior art by keyword, classification, or family.
- Pull full patent records (title, abstract, claims, description) for US patents.
- Cross-reference an EP/WO patent into its US family member to get full text.
Available MCP tools
| Tool | What it does |
|---|---|
search_patents_bigquery |
Keyword search across abstract / title / claims (US only for claims). |
get_patent_bigquery |
Full patent details by publication number. |
search_patents_by_cpc_bigquery |
Search by CPC classification prefix. |
search_patents_by_ipc_bigquery |
Search by IPC classification prefix (good for older or non-US patents). |
search_patent_family_bigquery |
All publications sharing a family ID across jurisdictions. |
check_bigquery_status |
Verify auth and quota project before a long workflow. |
Cost notes
BigQuery on-demand pricing is $6.25 / TiB (1 TiB free per month). The MCP server enforces a per-query bytes-billed ceiling, defaulting to 25 GiB. Override via PATENT_BIGQUERY_MAX_BYTES_BILLED if you need a larger scan window.
Choosing keywords
- 2-3 keywords work better than long phrases (BigQuery
LIKEmatching is literal). - For non-US patents,
claimsis empty in the dataset; the MCP keyword tool already searches title/abstract for those jurisdictions. For full text on EP/WO, use the EPO OPS tools instead. - Use
search_patent_family_bigqueryto bridge from an EP/WO hit to its US family member when you need claims.
Common workflows
Prior art sweep:
search_patents_bigquery(query=…, country="US")— broad scan.- Pick the top hits' CPC codes from
get_patent_bigquery. search_patents_by_cpc_bigquery(cpc_code=…)— pull adjacent technology.
Cross-jurisdiction lookup:
search_patents_bigquery(query=…, country="EP").- For any EP hit,
get_patent_bigqueryto get itsfamily_id. search_patent_family_bigquery(family_id=…)to find the US member with full claims.
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.
- 10d ago First seen · 48 lines · 37 tokens per session scan A d9a96562a888
patent-search is a skill published in the GitHub repository Raw1mage/patentmcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 577 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to patent-search, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…