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.
git 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/commands/raw1mage/patentmcp/create-epo-patent)<a href="https://agentmods.dev/commands/raw1mage/patentmcp/create-epo-patent"><img src="https://agentmods.dev/badge/commands/raw1mage/patentmcp/create-epo-patent.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.00016 | $0.02047 |
| Opus 5 | $0.00008 | $0.01024 |
| Sonnet 5 | $0.00003 | $0.00409 |
| Haiku 4.5 | $0.00002 | $0.00205 |
Grade B, and why
create-epo-patent scanned grade B with 1 finding 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 8d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Linux: `sudo apt install graphviz` This is a copy
100% identical to create-epo-patent — 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create EPO Patent Application
Guides you through creating a complete European patent application compliant with the EPC.
What This Command Does
Orchestrates the complete EPO patent application creation process:
- Prior Art Search (15-30 min)
- Claims Drafting (30-60 min)
- Specification Writing (60-120 min)
- Diagrams Generation (15-30 min)
- EPO Compliance Checking (15-20 min)
- Final Assembly (10-15 min)
Total Time: 2.5-4.5 hours for complete EP utility patent application
Process
Step 1: Gather Invention Information
I'll interview you about your invention:
- What problem does it solve?
- How does it work (high-level)?
- What are the key components or steps?
- What makes it novel/different from the closest prior art?
- Are there any working prototypes or examples?
- Is this a direct EP filing or Euro-PCT national phase entry?
Step 2: Prior Art Search
I'll search for relevant prior art using:
- BigQuery (100M+ worldwide patents, filter country="EP" for EP patents)
- EPO OPS API (European patent register, full-text EP documents)
- CPC classification search focused on EPO-heavy technology areas
Deliverable: Prior art search report with novelty/inventive step assessment
Step 3: Draft Claims (EPO Format)
I'll draft claims following EPO requirements:
Independent Claims (Rule 43(1) EPC):
- Two-part form: preamble + "characterised in that" + characterizing portion
- Based on closest prior art identified in Step 2
- Clear, concise, supported by description (Art. 84 EPC)
Dependent Claims:
- Proper back-references
- Further technical features
- Fallback positions for prosecution
Claim Categories:
- Product/apparatus claims
- Method/process claims
- Use claims (where appropriate)
- No method-of-treatment claims (Art. 53(c) EPC)
Deliverable: Complete claims section (15-25 claims, EPO two-part form)
Step 4: Write Specification (Rule 42 EPC)
I'll write the description following EPO section order:
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.
- 8d ago First seen · 250 lines · 16 tokens per session scan B 46ac0e6db1df
create-epo-patent is a command published in the GitHub repository Raw1mage/patentmcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 2,047 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). It is 100% identical to create-epo-patent, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
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.