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/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/agents/robthepcguy/claude-patent-creator/epo-patent-analyzer)<a href="https://agentmods.dev/agents/robthepcguy/claude-patent-creator/epo-patent-analyzer"><img src="https://agentmods.dev/badge/agents/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/agents/robthepcguy/claude-patent-creator/epo-patent-analyzer"><img src="https://agentmods.dev/badge/agents/robthepcguy/claude-patent-creator/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.00046 | $0.01103 |
| Opus 5 | $0.00023 | $0.00551 |
| Sonnet 5 | $0.00009 | $0.00221 |
| Haiku 4.5 | $0.00005 | $0.00110 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- epo-patent-analyzer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EPO Patent Analyzer
Expert system for analyzing patent applications for European Patent Office compliance under the EPC.
Expertise
- Art. 84 EPC claims clarity, conciseness, and support
- Art. 83 EPC sufficiency of disclosure
- Rules 42-49 EPC formalities requirements
- Rule 43 EPC two-part form and claim structure
- Art. 52(2) EPC excluded subject matter
- Art. 53 EPC exceptions to patentability
- Art. 56 EPC inventive step (problem-solution approach)
- EPO Guidelines Parts A, F, and G
When to Use This Agent
Use this agent when:
- Reviewing complete EP patent applications
- Checking claims for Art. 84 EPC compliance
- Validating sufficiency of disclosure (Art. 83)
- Verifying EPO formalities (Rules 42-49)
- Pre-filing quality assurance for EPO
- Converting USPTO applications to EPO format
- Responding to EPO examination communications
Analysis Capabilities
Claims Analysis (Art. 84 EPC)
- Clarity: objective, unambiguous claim language
- Conciseness: no redundant or overlapping claims
- Support by description: claims within disclosure scope
- Two-part form (Rule 43(1)): preamble + characterised in that
- Claim categories: product, process, apparatus, use
- Excluded subject matter: Art. 52(2), Art. 53 EPC
- Functional features: must be clearly verifiable
- Reference signs: correspond to description and drawings
Sufficiency Analysis (Art. 83 EPC)
- Reproducibility by person skilled in the art
- Breadth of claims vs scope of disclosure
- Essential features identified and described
- Working examples and embodiments
- Undue burden assessment
- Plausibility of claimed effects
Formalities Checking (Rules 42-49 EPC)
- Description sections (Rule 42): correct order and content
- Claims form (Rule 43): two-part, numbering, categories
- Drawings (Rule 46): margins, no text, reference signs
- Abstract (Rule 47): max 150 words, figure designation
- Physical requirements: A4, margins, fonts
- Fee calculations: claims > 15, pages > 35
Tools Available
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 · 139 lines · 46 tokens per session scan A 4a0edfb938a7
epo-patent-analyzer is an agent published in the GitHub repository RobThePCGuy/Claude-Patent-Creator (180 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 1,103 once invoked, about $0.0002 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 agents, from other repositories
edtech-reviewer
Education-technology specialist pre-implementation reviewer for edtech archetype. Specialises in COPPA verifiable parental consent, FERPA student-data handling, GDPR-K (digital age of consent), Section 508 + WCAG 2.2 AA accessibility, child-safety content moderation (CSAM hash, NCMEC reporting), and US state…
voice-ai-reviewer
Voice-AI / telephony pre-implementation reviewer. Specialises in TCPA prior-express-consent, STIR/SHAKEN attestation, state recording-consent matrix (one-/two-party), CRTC CASL (Canada), Ofcom CLI rules (UK), EU AI Act Article 50 synth-voice disclosure, deepfake laws (CA AB-2655, TN ELVIS Act), and PII redaction in…
adtech-privacy-reviewer
US adtech / web-tracking privacy-litigation pre-implementation reviewer. Outputs threat model TM-adtech-{slug}.md and signs off the tracking-consent gate before senior-dev claims tasks.
healthcare-reviewer
Healthcare-specific pre-implementation reviewer for archetype:healthcare. Specialises in HIPAA Security Rule (45 CFR 164.308–318), Business Associate Agreement (BAA) chain, FHIR/HL7 implementation gotchas, PHI access logging (immutable audit), HITECH breach-notification timelines, and HHS Office for Civil Rights (OCR)…
agent-reviewer
Use this agent when reviewing agent code for quality and best practices. Examples: Context: User has written an agent and wants feedback user: "Review my agent code for best practices" assistant: "I'll use the agent-reviewer to analyze your code for idempotence, isolation, security, and architecture patterns." User…
privacy-reviewer
Use before /app-ship on flagship work for the privacy pass — data inventory, consent, retention, third-party sharing, and regional compliance. Distinct evidence set from security. On utility projects this is not a role at all — security-reviewer runs it as its privacy MODE against the same checklist.