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 epo-patent-analyzergit 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/epo-patent-analyzer)<a href="https://agentmods.dev/skills/raw1mage/patentmcp/epo-patent-analyzer"><img src="https://agentmods.dev/badge/skills/raw1mage/patentmcp/epo-patent-analyzer/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/epo-patent-analyzer"><img src="https://agentmods.dev/badge/skills/raw1mage/patentmcp/epo-patent-analyzer.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.00051 | $0.02050 |
| Opus 5 | $0.00026 | $0.01025 |
| Sonnet 5 | $0.00010 | $0.00410 |
| Haiku 4.5 | $0.00005 | $0.00205 |
Grade A, and why
epo-patent-analyzer 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
100% identical to epo-patent-analyzer — 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EPO Patent Analyzer Skill
Automated analysis of patent applications for European Patent Office compliance under the European Patent Convention (EPC).
When to Use
Invoke this skill when users ask to:
- Review patent claims for EPO Art. 84 compliance
- Check sufficiency of disclosure under Art. 83 EPC
- Analyze EPO formalities under Rules 42-49 EPC
- Convert USPTO-style claims to EPO two-part form
- Prepare for EPO examination or respond to EPO communications
- Validate applications before EP filing or Euro-PCT entry
What This Skill Does
Performs comprehensive EPO-focused analysis:
-
Claims Analysis (Art. 84 EPC):
- Clarity: identifies unclear or ambiguous terms
- Conciseness: detects redundant or overlapping claims
- Support: verifies all claims are supported by description
- Two-part form (Rule 43(1) EPC): checks preamble + "characterised in that"
- Claim categories: product, process, apparatus, use
- Excluded subject matter: Art. 52(2) and Art. 53 EPC
-
Sufficiency of Disclosure (Art. 83 EPC):
- Reproducibility: can a person skilled in the art reproduce the invention?
- Breadth of claims vs disclosure: is the full scope enabled?
- Essential technical features: all present and described?
- Working examples: at least one concrete embodiment?
-
Formalities (Rules 42-49 EPC):
- Description format (Rule 42): required sections in correct order
- Claims form (Rule 43): two-part form, numbering, references
- Drawings (Rule 46): margins, no text, reference signs
- Abstract (Rule 47): max 150 words, figure designation
- Physical requirements: A4, margins, fonts
-
Issue Categorization:
- Critical: Will cause objection under EPC
- Important: May cause objection or limit scope
- Minor: Best practice per EPO Guidelines
Required Data
This skill uses the EPO compliance analyzers and the EPC/EPO Guidelines search:
MCP Tools Available:
review_epo_claims- Art. 84 EPC compliance checkingreview_epo_specification- Art. 83 EPC sufficiency analysischeck_epo_formalities- Rules 42-49 EPC formalitiessearch_patent_law- Search EPC, EPO Guidelines, PCT rules
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 · 223 lines · 51 tokens per session scan A f602b6a0579d
epo-patent-analyzer is a skill published in the GitHub repository Raw1mage/patentmcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 2,050 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to epo-patent-analyzer, differing in 0 lines, and is treated as a copy.
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.
regulatory-research-fallback
Fallback workflow for regulatory research when web extraction tools fail on government PDFs.
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.
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.
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…
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…