Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Raw1mage/patentmcp/plugin install claude-patent-creator-standaloneWrote 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/commands/raw1mage/patentmcp/setup-patent-system)<a href="https://agentmods.dev/commands/raw1mage/patentmcp/setup-patent-system"><img src="https://agentmods.dev/badge/commands/raw1mage/patentmcp/setup-patent-system.svg" alt="Measured on agentmods" 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.00022 | $0.01437 |
| Opus 5 | $0.00011 | $0.00718 |
| Sonnet 5 | $0.00004 | $0.00287 |
| Haiku 4.5 | $0.00002 | $0.00144 |
Grade A, and why
setup-patent-system 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 6d 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
100% identical to setup-patent-system — 0 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Patent Creator System
Complete one-time setup for all patent creator capabilities.
What This Does
The patent-creator setup CLI handles everything automatically:
- Detect GPU and install PyTorch with correct CUDA version
- Download MPEP PDFs (500MB) - USPTO examination manual
- Download Legal Sources - 35 USC, 37 CFR, Federal Register updates
- Build Search Index - FAISS + BM25 hybrid search (5-65 min depending on GPU)
- Configure MCP server registration with Claude Code
Total Time: 30-90 minutes (most time is MPEP download and index building)
Requirements
- Python 3.9-3.12 (3.11 recommended). Python 3.13+ may lack wheels for PyTorch/FAISS.
- 8GB+ RAM (16GB for index building)
- 5GB free disk space
- Internet connection (for downloads)
- Optional: NVIDIA GPU (10x faster index building)
Process
Step 1: Find Compatible Python
Python 3.13+ will NOT work — PyTorch and FAISS may not have wheels. Find 3.9-3.12:
# Check default
python --version 2>&1
# If 3.13+, look for compatible versions:
# Windows (py launcher):
py -3.12 --version 2>&1
py -3.11 --version 2>&1
py -3.10 --version 2>&1
# Linux/macOS:
python3.12 --version 2>&1
python3.11 --version 2>&1
Use the first compatible version found (3.9-3.12). Remember this as PYTHON_CMD for all remaining steps.
If no compatible Python is found, tell the user to install Python 3.12 from python.org.
Step 2: Create venv and Install Package
cd ${CLAUDE_PLUGIN_ROOT}
${PYTHON_CMD} -m venv venv
Use the venv Python for all remaining commands:
- Windows:
${CLAUDE_PLUGIN_ROOT}/venv/Scripts/python - Linux/macOS:
${CLAUDE_PLUGIN_ROOT}/venv/bin/python
Install the package:
${VENV_PYTHON} -m pip install --upgrade pip
${VENV_PYTHON} -m pip install -e .
Step 3: Run Automated Setup
The patent-creator setup CLI handles GPU detection, PyTorch installation, MPEP downloads, and index building automatically:
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.
- 6d ago First seen · 167 lines · 22 tokens per session scan A 515f2a3721d8
setup-patent-system is a command published in the GitHub repository Raw1mage/patentmcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 1,437 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to setup-patent-system, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
voice-compliance
Voice/telephony compliance check — invokes voice-ai-reviewer to produce TM-voice-{slug}.md with TCPA, STIR/SHAKEN, state recording-consent, EU AI Act Art. 50, and synth-voice deepfake-law gaps.
review-policy
Review a policy document for structure, coverage, and language quality.
at-dsgvo
You are helping an enterprise architect generate an Austrian Data Protection Assessment — the Austrian-specific GDPR layer applied by the Datenschutzbehörde (DSB) under the Datenschutzgesetz (DSG 2018, BGBl. I Nr. 165/1999 as amended). Run this after /arckit:eu-rgpd to add Austrian obligations that go beyond the EU…
au-pspf
You are an enterprise architect generating a Protective Security Policy Framework (PSPF) compliance assessment for an Australian Government entity or contractor handling government information.
compliance-audit
Full regulatory compliance audit for GDPR, HIPAA, SOC2, PCI-DSS, ISO 27001, and other frameworks with gap analysis, remediation planning, and evidence collection.