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 RobThePCGuy/Claude-Patent-Creator --skill epo-patent-analyzergit clone --depth 1 https://github.com/RobThePCGuy/Claude-Patent-CreatorWrote 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/robthepcguy/claude-patent-creator/epo-patent-analyzer)<a href="https://agentmods.dev/skills/robthepcguy/claude-patent-creator/epo-patent-analyzer"><img src="https://agentmods.dev/badge/skills/robthepcguy/claude-patent-creator/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/robthepcguy/claude-patent-creator/epo-patent-analyzer"><img src="https://agentmods.dev/badge/skills/robthepcguy/claude-patent-creator/epo-patent-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 5 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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 11d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- epo-patent-analyzer — 100% identical, 0 lines differ
- epo-patent-analyzer — 100% identical, 0 lines differ
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.
- 11d ago First seen · 223 lines · 51 tokens per session scan A f602b6a0579d
epo-patent-analyzer is a skill published in the GitHub repository RobThePCGuy/Claude-Patent-Creator (181 stars, last pushed 2d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
plagiarism-checker
Scans lyrics for phrases that may match existing songs using web search and LLM knowledge. Use before release to check for unintentional borrowing.
compensation-and-leveling
Builds and maintains the leveling framework and pay structure — level definitions, salary bands, benchmarking, pay equity, and how raises and promotions are decided. Use this to design or revise leveling, set or adjust salary bands, benchmark against market, handle a compensation request or counteroffer, run a review…
employment-compliance
Covers the employment rules that carry real penalties — exempt and non-exempt classification, overtime and hours, employee versus contractor status, work authorization and recordkeeping, accommodation requests, and the notices and retention obligations that go with them. Use this to classify a role, review a…
sanity-best-practices
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, webhooks, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this…
video-perception
Use when the user mentions a video file (.mp4, .mov, .avi, .mkv, .webm), a YouTube URL, asks to watch/analyze/review a video, or references video content in conversation.
tax-ebookkeeping-context
Background information about Japan’s Electronic Bookkeeping Act, which sets rules for storing accounting records, scanned documents, and data received through electronic transactions.